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

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.