Accessing getters within Vuex mutations

Question

Within a Vuex store mutation, is it possible to access a getter? Consider the below example.

new Vuex.Store({     state: {         question: 'Is it possible to access getters within a Vuex mutation?'     },     mutations: {         askQuestion(state) {             // TODO: Get question from getter here             let question = '';              if (question) {                 // ...             }         }     },     getters: {         getQuestion: (state) => {             return state.question;         }     } }); 

Of course the example doesn't make much sense, because I could just access the question property directly on the state object within the mutation, but I hope you see what I am trying to do. That is, conditionally manipulating state.

Within the mutation, this is undefined and the state parameter gives access to the state object, and not the rest of the store.

The documentation on mutations doesn't mention anything about doing this.

My guess would be that it's not possible, unless I missed something? I guess the alternative would be to either perform this logic outside of the store (resulting in code duplication) or implementing an action that does this, because actions have access to the entire store context. I'm pretty sure that it's a better approach, that is to keep the mutation focused on what it's actually supposed to do; mutate the state. That's probably what I'll end up doing, but I'm just curious if accessing a getter within a mutation is even possible?

Answer 1

Vuex store mutation methods do not provide direct access to getters.

This is probably bad practice*, but you could pass a reference to getters when committing a mutation like so:

actions: {   fooAction({commit, getters}, data) {     commit('FOO_MUTATION', {data, getters})   } }, mutations: {   FOO_MUTATION(state, {data, getters}) {     console.log(getters);   } } 

---

* It is best practice to keep mutations a simple as possible, only directly affecting the Vuex state. This makes it easier to reason about state changes without having to think about any side effects. Now, if you follow best practices for vuex getters, they should not have any side effects in the first place. But, any logic that needs to reference getters can run in an action, which has read access to getters and state. Then the output of that logic can be passed to the mutation. So, you can pass the reference to the getters object to the mutation, but there's no need to and it muddies the waters.