There is now a debate whether or not you need redux, with the release of react hooks and the context API. We have previously suggested a custom Hook called usePrevious to hold the previous value. However, we\u2019ve found that most use cases fall into the two patterns described above.<\/p>\n
<\/p>\n
Make sure everyone on your team is on board with using them and familiar with this documentation. We don\u2019t recommend rewriting your existing classes to Hooks unless you planned to rewrite them anyway (e.g. to fix bugs). Recoil is a fairly new state management tool developed by Facebook. In Recoil, each piece of state is called an atom, and atoms can be combined with selectors. You can combine atoms and selectors to create data structures unique for your application. The idea is that the setvalue function fires an event with a parameter carrying the value and the event handler updates the hooks internal state.<\/p>\n
If you need to test a custom Hook, you can do so by creating a component in your test, and using your Hook from it. From React\u2019s point of view, a component using Hooks is just a regular component. If your testing solution doesn\u2019t rely on React internals, testing components with Hooks shouldn\u2019t be different from how you normally test components. There are no plans to remove classes from React \u2014 we all need to keep shipping products and can\u2019t afford rewrites. We’re not encouraging you to use these tools, nor we’re saying they are better than Redux or Context API.<\/p>\n
<\/p>\n
This was a very trivial example to demonstrate the power of Redux. As you can imagine, Redux can be used to handle much more complex states. Context is ideal to use for sharing global data such as current authenticated user, theme, or the user language. The store has one responsibility, that responsibility is to hold the application state. It is highly encouraged to keep only one store in any application that uses Redux. The job of the provider is to define and track certain pieces of state.<\/p>\n
After completing this piece, I happened upon a clear and concise summary of different ways to use React hooks to manage global state. Daishi Kato does a great job of exploring the pros and cons of each approach, and the two libraries he\u2019s written around Redux and React Hooks state management look really interesting. I highly recommend heading over there if you\u2019re interested in digging deeper. This is great for performance, because it allows us to pass down just the pieces of app state that our components require, which cuts down on unnecessary re-renders when unrelated pieces of the state change. However, It also increases the number of components we need to build and maintain.<\/p>\n