@atomico/store
@atomico/store a more predictable and natural model for asynchrony when controlling states.
Last updated
@atomico/store a more predictable and natural model for asynchrony when controlling states.
Last updated
Asynchrony management.
Finitely predictable asynchrony.
Modularity and composition.
Application events and service calls are naturally asynchronous, with @atomico/store you can use asynchronous functions or asynchronous generators to define the update cycle.
update cycle? By this I mean the states that occur sequentially when dispatching the action, example:
The previous action will generate 2 states when dispatched:
state 1:{loading: true, products:[]}
state 2: {loading: false, products:[...product]}
The advantage of this is that the process is clearly observable by the store and by whoever dispatches the action.
Every action in @atomico/store is wrapped in a promise that defines when it ends its cycle, this will let you execute actions sequentially, example:
@atomico/store allows to decouple the actions and the state of the store, for a better modularization , example: