Skip to main content

mapState, mapGetters, mapMutations, mapActions in vuex

 The above four objects are all in the vuex plug-in store, which is often used to store some data shared globally. But I still feel a little uncomfortable when using it, that is, I wrote a lot of repeated prefixes. At this time, these four objects appeared, which solved this pain point very well. mapState is mainly used to manipulate and obtain data, mapGetters is equivalent to computed properties, and mapMutations and mapActions are simplifications of mutation and action. They can be written as both objects and arrays.

Steps for usage

  • Install vuex: >>>npm install vuex (note the version, vue2-vuex3, vue3-vuex4)
  • Vue officially recommends writing an index.js file in the store folder, configuring various configuration items, then registering it on Vue, and exposing the ones to be used.

import Vue from "vue"
import Vuex from "vuex"
const actions={
  addOddnum(context,value){
            context.commit("Idnum",value)
       /*  console.log("Act1...")
        context.dispatch("Act1",value) */
    },
    //
    /* Act1(context,value){
        console.log("Act2...")
        context.dispatch("Act2",value)
    },
    Act2(context,value){
        console.log("Act2 Now do it")
            context.commit("AddOddnum",value)
    }, */
 
}
const mutations={
    Idnum(state,value){
        console.log(state)
        console.log(value)//default enents
        state.sum+=value
    },
...  
}
//
const getters={
    he(state,b,c,d){
       /*  console.log(state)
        console.log(b)//undefined
        console.log(c)
        console.log(d) */
        return state.id+100
    }
}
//
const state={
    id:100,
    name:"aaa"
        }

Vue.use(Vuex)
export default new Vuex.Store({
    actions,
    mutations,
    getters,
    state
})

  • Introduced in main.js
import store from "./store/index"

Vue.config.productionTip = false;
const vm=new Vue({
  render: h => h(App),
  store,
}).$mount('#app');

  • It can work next

 computed:{
      // ...mapState({key:value,...})
      ...mapState([value,...]),
      // ...mapGetters(["value"])
      ...mapGetters({key:value}),
      //
  },
methods: {
 
     ...mapMutations({key:value}),
   
     ...mapActions({key:value})
  },

Comments

Popular posts from this blog

What is the difference between width property 100% and auto in css?

 width:auto: The default width value of block-level elements. When set to this value, the browser will automatically select an appropriate width value to adapt to the width of the parent element. When the width is set to 100%, the width of the child element box The value is equal to the parent's content, and as the parent's content automatically changes, after adding the padding and margin of the child element, its width remains unchanged, which is the difference from setting it to auto. But we most often use width:auto, because it is more flexible, width:100% is used less, because when adding padding or margin, this method is easy to make it exceed the parent box and destroy the original layout.

Access to XMLHttpRequest at 'http://localhost:8080/xxx' from origin 'http://localhost:8080' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.

 Due to browser same-origin policy restrictions. The Same Origin Policy is a convention. This is the main and essential security feature of the browser. Without the same-origin policy, normal browser functionality may be affected. The web is built on the same-origin policy, and browsers are just one implementation of the same-origin policy. The Same Origin Policy prevents JavaScript scripts from one domain from interacting with content from another domain. The so-called same origin (that is, the same domain) means that two pages have the same protocol, host and port.