You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Vue Class Store is fundamentally different from Vuex in that it doesn't have a wider state management methodology such as explicit one-way data flow, but it is designed to be easy to use and bridge the "shared state" gap between component state and full-Flux global state.
Many developers are used to working exclusively with Vuex – for all its benefits and drawbacks – and understandably have concerns about moving away from something tried and trusted.
Discussion (WIP)
This raises various questions, which should be explored.
Methodology:
does it / when does it matter if you don't use Flux-style one-way data flow?
Background
Vue Class Store is fundamentally different from Vuex in that it doesn't have a wider state management methodology such as explicit one-way data flow, but it is designed to be easy to use and bridge the "shared state" gap between component state and full-Flux global state.
Many developers are used to working exclusively with Vuex – for all its benefits and drawbacks – and understandably have concerns about moving away from something tried and trusted.
Discussion (WIP)
This raises various questions, which should be explored.
Methodology:
Compatibility:
Differences:
Tooling:
Contributing
Please add any thoughts below as a comment, and I will update the list above as appropriate to for a TOC as it were.
The text was updated successfully, but these errors were encountered: