M
I use redux and everything that goes on to him, I don't say anything about flux, it's all mud before, a lot of reality, and so on.So, ideally, you're keeping the annex in store, that's all. Filled the form field - stored, changed the button in store, downloading the data - the loading flag should be stored, data downloaded - should be stored. But the world isn't perfect, so small things, like, "the state of the stoves: turned" are better stored locally in a state component.Plus:It's a good job, undo/redo.You can literally keep the store in the wrong way and retrieve yourself.minimum shadow logic, searching for theah is very simple.Almost all the components of a stateless... just the render of the very condition.You have a huge object with all the data from the application. But you don't need it for every component that you use. reselect He's pulling a small object with data from the general state of optimization, working really cool, afraid of a huge store with it.By the way, you can use the data for download. redux-api (not the most exquisite solution, but rather powerful) and react-redux-form (so stunning).Look at a series of screenwriters from the redux developer, a lot of questions off.
https://egghead.io/lessons/javascript-redux-the-single-immutable-state-tree