Skip to main content

How to execute when props and methods method name conflict?

 The props property in Vue is used to pass values between components. Its main function and meaning is to receive data from the outside. It is equivalent to data and methods.When the attributes in the newly added mixins.js file conflict with the attributes in the component, such as the data attribute, methods attribute, etc., the attributes in the component shall prevail. If there is no conflict, the incoming props will be executed. But there are special ones: when there is a conflict between the lifecycle hook functions, the hooks passed in by props or in mixins.js are used first.

The following is an actual small demonstration case

//mixins.js
export const mix=
methods: {
        show(){
            alert("11111");
        }
    }
}
//App.vue
export default {
    name: "Student",
methods:{
        show(){
          alert("666600000!!!");
        }    
}

Resulat://666600000!!!



Comments

Popular posts from this blog

favicon.ico 404 Not Found Causes and Solutions

 What is favicon? It is the abbreviation of Favorites Icon. Its function is that in addition to displaying the corresponding title in the browser's favorites, icons can also be used to distinguish different websites. When I encounter this kind of error, I feel very uncomfortable. There is obviously no problem. Why is a 404 error reported? The following is the solution.

Use of custom events in Vue components.

 The parent component uses props to pass data (such as a method) to the child component, and the child component needs to use custom events to pass data back to the parent component! We can use v-on to bind custom events, and then pass them to subcomponents, which will call after receiving the method. Each Vue instance implements the Events interface, that is: use $on(eventName) to listen for events and $emit(eventName) to trigger events.

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.