Skip to main content

watch event listener in vue2

 what is watch? It is an expression or method that monitors changes to a Vue instance. The callback function gets the new value and the old value as arguments, replaced by a function. Simply put: the role of watch can monitor the change of a value, and then call the method that needs to be executed because of the change. You can dynamically view the changes of the instance through watch, and you can also make further operations.

The properties of the watch can be configured:

  • immediate:true/false//Executed once when the instance object is initialized
  • deep:true //will monitor all properties in the object
  • handler()//Some custom operations can be performed in this function
  • Note that you should not use arrow functions to define watcher functions
  • The watch monitoring method can only monitor one variable at a time. Simply using watch cannot monitor multiple variables, but we return an object through the computed computed property, and then use watch to monitor the method of this computed property. As long as the value changes, the watch will be triggered. 

Next, look at the actual code:

    <div id="app">
        <input type="text" v-model="id"><br/>
        <input type="text" v-model="name"><br/>
        <button @click="IdAdd">clicl</button>
        <p>{{result}}</p>

    </div>

    <script>
     Vue.config.productionTip=false
        var vm = new Vue({
            el: '#app',
            data: {
                id:1001,
              name:"aaa",
               obj:{
                    hobby:"sing"
               }
            },
            methods: {
                IdAdd(){
                    this.obj.hobby="swim";
                    this.id+=100;
                }
            },
            computed:{
                result(){
                    this.obj.hobby="swim";
                    return this.id+"---"+this.name;
                }
            },
            watch:{
/*                 result:{
                    immediate:true,
                    deep:true,
                    handler(oldValue,newValue){
                        console.log("changed...",oldValue,newValue);
                    }
                },  */                            
                "obj.hobby":{
                    handler(oldValue,newValue){
                        console.log("changed...Hobby",oldValue,newValue);
                    }  
                },
/*                 'IdAdd':{
                    handler(){
                        console.log("changed...ID",oldValue,newValue);
                    },
                } */
            }
        });
    </script>

Another way of writing watch

        vm.$watch("obj.hobby",{
           
            immediate:true,
            deep:true,
            handler(oldValue,newValue){
                console.log("changed...Hobby",oldValue,newValue)
            }
        })


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.