React

Lots of internet ink has been spilled over when to keep data in an application state management system (like Redux) versus in a React component’s internal state. While I have mentioned benefits to Redux before, it’s important to understand the tradeoffs.

In hybrid Rails/React projects, assets often need to be shared between the Rails asset pipeline and your Javascript environment. If you’re using the Webpacker gem, here’s how to include Rails asset paths in your bundle:

Hybrid Rails and React projects are a pretty common thing these days. So much so that Yarn and Webpack have been better integrated into Rails 5.1.

Friendly reminder: React components don’t have to render any markup. It’s totally okay to do this:

render() { return null; }

If you’ve tried other Middlewares in Redux, like Redux Thunk, and have found them difficult to read and maintain, it may be worth trying redux-saga.

Lots of our React/Redux projects at 20spokes require many different things to happen when a user…