3 . Keep your data in a Store/model, you have the latest data anytime while keeping the "single source of truth"
Hi @bgadrian , did you mean using libraries such as Redux/MobX?
That would be one way yes.
The idea is that if you need a state object and the React way is a problem you can move it to a model. I would not recommend it for something simple like your examples of course, just stating that this possibility exists.
That sounds like a spot-on idea.
I recently created a small web page and used MirrorJS (uses Redux underneath) to keep all states in one place.
setState wasn't needed in most of places and all the states were managed in one place.
setState
Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink.
Hide child comments as well
Confirm
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.
3 . Keep your data in a Store/model, you have the latest data anytime while keeping the "single source of truth"
Hi @bgadrian , did you mean using libraries such as Redux/MobX?
That would be one way yes.
The idea is that if you need a state object and the React way is a problem you can move it to a model. I would not recommend it for something simple like your examples of course, just stating that this possibility exists.
That sounds like a spot-on idea.
I recently created a small web page and used MirrorJS (uses Redux underneath) to keep all states in one place.
setState
wasn't needed in most of places and all the states were managed in one place.