is it bad practice to access vuex state properties directly (without getters), and why?

user_2773445 0
Viewed 10315

If here is my store.js file:

const state = {
  count: 0,
  loggedIn: false
}

const mutations = {
  UP_COUNT(state) {
      state++;
  }
}

const actions = {
  upCount({ commit }) {
    commit('UP_COUNT');
  }
}


Let's say to increase state count from one of my Vue components, I will call an action which then commits a mutation:

this.$store.dispatch('upCount');


Then let's say in another Vue component, I want to use the state count:

<div class="count">{{ this.$store.state.count }}</div>


What is wrong with this style? (vs using $this.store.getters...)

vuejs2 vuex vue.js getter-setter javascript
1 Answers

As I pointed out on this post there is no hard and fast way you must do things but following a practice and going with it is best.

Using getters might seem over-kill but you can change the data behind the scenes using getters as long as the getter name remains the same and this saves a lot of work re-factoring and trying to find all the references to other places where you might have used this.$store.state.module.someValue.

It also allows you to return data based on mutiple state variables into one getter i.e 

`isAllowed: 'getIsAllowed'`

could be based on 

getIsAllowed (state) {
  return state.loggedIn && state.hasPermission && state.somethingElse
}

You can change what isAllowed is based on easily in one place rather than using each state variable in your components and doing the logic multiple times.

user_2616820
Related