Published October 2016
Developing a Redux Edge
Redux aims to decouple state mutation and asynchronicity, separating them so that you can reason about them individually. If you have a problem with state, you can debug the state tree to determine how the state was created without having to worry about asynchronous logic. Likewise, if you have a problem with your asynchronous logic, you can focus on debugging it without having to worry about state. This opens up a range of additional benefits, ranging from improvements to developer workflows to easier unit testing. All of this due to the separation of asynchronous logic from state mutation.
- CHAPTER 1: Why Use Redux?
- CHAPTER 2: Core Concepts
- CHAPTER 3: Redux Patterns
- CHAPTER 4: Building the Sample App
- CHAPTER 5: Syncing Data with the Server
- CHAPTER 6: Showing Request State to Users
- CHAPTER 7: Persisting State on Client
- CHAPTER 8: Analytics Middleware
- CHAPTER 9: Best Practices
- CHAPTER 10: Going offline