Detailed explanation of vuex project structure directory and configuration usage

This time I will bring you a detailed explanation of the use of the vuex project structure directory and configuration. What are the precautions when using the vuex project structure directory and configuration. The following is a practical case, let's take a look.

First of all, here is a serious "advice" from the official website:

The rules that vuex needs to abide by:

1. Application-level state should be concentrated into a single store object.

2. Submitting a mutation is the only way to change the state, and this process is synchronous.

3. All asynchronous logic should be encapsulated into action.

FilesDirectory structure

Relationship between files:

store folder-storage vuex series File

store.js - Introduce vuex, set state data, introduce getter, mutation and action

getter.js - Get the status in the store

mutation.js - The storage place of the function used to change the state in the store

action.js - Submit mutation to modify the state tactfully, and can operate asynchronously

Simple and common writing method

store.js file:

import Vue from 'vue'
import Vuex from 'vuex'
import actions from './actions'
import mutations from './mutations'
Vue.use(Vuex)
const state = {
 a: '初始值',
 b: 'balabala...'
}
export default new Vuex.Store({
  state,
  actions,
  mutations
})

In the main.js file (inject the store from the root component, just like injecting the router):

By registering the store option in the root instance, the store The instance will be injected into all sub-components under the root component, and sub-components can be accessed through this.$store.

import store from './store/index'
new Vue({
 el: '#app',
 router,
 store,
 ...
})

Simple configuration of Getter.js (store's computed properties, accepting state as a parameter)

export default {
  doneTodos: state = >{
   return state.todos.filter(todo = >todo.done)
  }
}

Get (inside the computed properties of a component):

computed: {
 doneTodosCount () { 
  return this.$store.getters.doneTodosCount 
 }
}

can be passed Simple configuration of the getter attribute of the parameter

export default{
 getTodoById: (state) => (id) => { 
  return state.todos.find(todo => todo.id === id) 
 }
}

Get (inside the calculated property of a component):

computed: {
 getTodoById() { 
  return this.$store.getters.getTodoById(‘参数')
 }
}

mutation.js Simple configuration:

export default {
  increment(state) {
   //变更状态
   state.count++
  }
}

Trigger (in the component)

this.$store.commit(state,payload)
actions.js简单配置：
export default{
 action (context) {
 //异步操作
  setTimeout（（）=>{
   //变更状态
   context.commit('mutationFunName'，value)
  }）
 }
}

Trigger (component)

this.$store.dispatch('mutationFunctionName')
2018-04-07 18:13:34

I believe you have mastered the method after reading the case in this article. For more exciting information, please pay attention to other related articles on the PHP Chinese website!

Recommended reading:

vue-router lazy loading steps to solve the slow first loading speed

vue2.0 resource file Instructions for using assets and static

Detailed explanation of using Router in Angular 5.x

The above is the detailed content of Detailed explanation of vuex project structure directory and configuration usage. For more information, please follow other related articles on the PHP Chinese website!