Whichever one you end up settling on for this project, I'd specifically recommend that you take some time to look at our Redux Style Guide docs page, which lists our recommended patterns and best practices, and try out our new Redux Toolkit package, which is our official recommended approach for writing Redux logic. RTK includes utilities to simplify several common Redux use cases, including store setup, defining reducers, immutable update logic, and even creating entire "slices" of state at once.
Finally, as others have mentioned, we're also generally recommending that you should use the React-Redux hooks API as the default UI layer.
Hi, I'm a Redux maintainer.
Whichever one you end up settling on for this project, I'd specifically recommend that you take some time to look at our Redux Style Guide docs page, which lists our recommended patterns and best practices, and try out our new Redux Toolkit package, which is our official recommended approach for writing Redux logic. RTK includes utilities to simplify several common Redux use cases, including store setup, defining reducers, immutable update logic, and even creating entire "slices" of state at once.
Finally, as others have mentioned, we're also generally recommending that you should use the React-Redux hooks API as the default UI layer.
Somehow I had missed the Redux Style Guide - what a great collection of tips and practices. Thank you for sharing!
Sure. We've had a few folks say we need to make that more visible somehow. If you've got any suggestions, let me know.