Summary
In this chapter, you learned how to refine your Flux architecture using the Redux library. Redux applications should have only one store, action creators can be simple, and reducer functions control the transformation of the immutable state. The aim of Redux, in a nutshell, is to reduce the number of moving parts typically found in a traditional Flux architecture while retaining the unidirectional dataflow.
You then implemented the Snapterest application using Redux. Starting with the reducers, you returned a new state for the Redux store any time a valid action was dispatched. Then you built action creator functions that returned an object with the correct type property. Lastly, you refactored components so that they were connected to Redux. You made sure that the components could read store data as well as dispatch actions.
This is a wrap for this book. I hope you've learned enough about the essentials of React development that you can continue your journey of discovery by...
