Middleware is one of the most powerful and useful features of redux. If you’re unfamiliar with redux middleware, basically it is a way to insert extra behavior into dispatched redux actions.
Today we’re going to use it to make a clean and powerful way to manage our subscriptions to different Action Cable channels+rooms this also means taking the data sent to use through action cable and dispatching the appropriate redux actions to mutate the state.
Linters can be annoying at first, but I feel like they really help me write better code. Plus they are great for working in teams to make sure everyone is following the same conventions.
We’re going to walk through how to setup ESLint and add it to our project using a git pre-commit hook.
Why I prefer Styled Components
I prefer Styled Components because I feel like it is more inline with the core component philosophy of react. React is all about creating reusable components, and really pushed the idea of bundling the templating (HTML) and behavior (JS) together into components. So it always felt a bit wonky to me to still put my CSS in a separate file and connect my styling using regular CSS
With the facebook API, page tokens can often be used in place of user tokens. This is very useful because if you are doing something with a business, its not ideal to have to use your own user token for everything. However, if you don’t want to have to recreate a new token all the time, you have to go through the process of getting a long-lived page access token.
Express.js doesn’t come with es6 out of the box. But its actually not that hard to add.
I’m going to go over how to easily add ES6 support to your project using the babel-cli, as well as show you some of the things you need to do so your app will be ready for production later.