0 - 100 Real Quick...with Redux
We’ve all been there before.
You finally get some time to work on that little project you’ve been dying to work on for the last couple of months. You have all the awesome features you want your application to include in your head and you’re ready to go to town on your keyboard.
Day 1:
You’ve set up your git, your npm packages and your project structure and start working on your first feature. You finish the day out getting that one feature nice and polished.
Day 2:
You get working on your second feature and the ramp time is a little slower to get out. You’re finding it a little difficult to juggle the state of your app. Should state go here? But wait, I need that state in my other object!
And this is where Redux comes into the picture.
Redux
As described by Dan Abramov of the library:
Redux is a predictable state container for JavaScript apps.
Redux provides an awesome tool for web developers to address the inevitable issue of managing the growing complexity of application state.
How does Redux solve my problems?
Redux abides by 3 principles:
1. The “Single Source of Truth” 2. State is read-only
3. State can only change with pure functions
