Putting everything in Redux will often be too heavy handed, particularly for aspects like visual states (show/hide/expand/style content); however, data values attributes I will put within the global state as for me it is easier to track when, how, and what data is changing to.
I also find the issue of having some data values being handled within local state, and other within global state a nuisance to debug.
I completely agree with this, I find the idea of putting visual state in a store mental no matter how big the app is.
In my case I use a setup where flux stuff is shared between react and react native so all data is decoupled from platforms which just feels correct to me as it could “live” anywhere, even on the server.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Putting everything in Redux will often be too heavy handed, particularly for aspects like visual states (show/hide/expand/style content); however, data values attributes I will put within the global state as for me it is easier to track when, how, and what data is changing to.
I also find the issue of having some data values being handled within local state, and other within global state a nuisance to debug.
I completely agree with this, I find the idea of putting visual state in a store mental no matter how big the app is.
In my case I use a setup where flux stuff is shared between react and react native so all data is decoupled from platforms which just feels correct to me as it could “live” anywhere, even on the server.