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
The motivation of encapsulating more of the Vuex functionality is to extend the type-safety to more parts of Vuex.
Root Vuex Module
The first step would be to encapsulate the creation of the root Vuex module, then we can also pass pre-made proxies to actions and getters.
To do this we are missing options for plugins, strict, and devtools.
We could implement decorators for Watch, Subscribe, and SubscribeAction. This way we could have actions or mutations be called as reactions to other parts of the state without the origin knowing what methods to call after a change. I.e. Fetch different kinds data after login state changed/login action is called/login mutation is called without them knowing what actions or mutations that relies on it.
The text was updated successfully, but these errors were encountered:
The motivation of encapsulating more of the Vuex functionality is to extend the type-safety to more parts of Vuex.
Root Vuex Module
The first step would be to encapsulate the creation of the root Vuex module, then we can also pass pre-made proxies to actions and getters.
To do this we are missing options for
plugins
,strict
, anddevtools
.Class decorator
Constructor options
Configuring sub-modules
Other possibilities
We could implement decorators for
Watch
,Subscribe
, andSubscribeAction
. This way we could have actions or mutations be called as reactions to other parts of the state without the origin knowing what methods to call after a change. I.e. Fetch different kinds data after login state changed/login action is called/login mutation is called without them knowing what actions or mutations that relies on it.The text was updated successfully, but these errors were encountered: