Note including all the parameters here is important. If you do not include all four and you want to use rootGetters for example:

someGetter (state, rootGetters) {

rootGetters will be getters because getters is the second argument passed to this function and so you will not actually be on the root scope but instead the local scope.

To access rootGetters in another name spaced module:

someGetter (state, getters, rootState, rootGetters) {
  let value = rootGetters["module-name/getterName"](param1);

Handling forms in vuex - use computed properties with a getter and a setter,

the getter - pulls the value from the store the setter - commits the value to the store

This is a common pattern I've seen with people adopting tools like [[redux]] or [[Vuex]] for [[state management]] without understanding the [[problems that state management tools aim to solve]]

• [[Its ok to have local state]]
• [[Not all state needs to be app state]]

Not only does putting all of the state into the store cause extra indirection, it can make things complicated if you are putting in state that is tied to the lifecycle of a component - needing to clear / reset the state the next time it loads.

It can also add complications when you have multiple instances of a component - and trying to make all of it's state got into Vuex - for example, if you had multiple carousel components on a screen - would there be value in trying to manage that state in vuex?

Actions are asynchronous vs mutations which as synchronous.

So for example an action may be a combination of mutation calls and async api calls.