Skip to main content

Advantages of vue computed properties

 A computed property is that when the value of its dependent property changes, the value of this property will be automatically updated, and the DOM part related to it will also be updated automatically. Although inline expressions can be used to achieve very simple effects, it is inconvenient to use in complex scenarios. The most suitable use scenarios are simple Boolean operations or string concatenation. If more complex business logic is involved, you should preferably use computed properties.

The following is a direct comparison of three examples

  • Use expressions directly to get values

   <div id="app">
        number1:<input type="text" v-model="num1"><br/>
        number2:<input type="text" v-model="num2"><br/>
        sumResu:<p>{{parseInt(num1)+parseInt(num2)}}</p>
    </div>

    <script>
        Vue.config.productionTip=false;
        var vm = new Vue({
            el: '#app',
            data: {
                    num1:10,
                    num2:20
            },
        });
    </script>

  • Expressions combined with methods to evaluate

    <div id="app">
        number1:<input type="text" v-model="num1"><br/>
        number2:<input type="text" v-model="num2"><br/>
        <!-- sumResu:<p>{{parseInt(num1)+parseInt(num2)}}</p> -->
        sumResu:<p>{{Sum()}}</p>

    </div>

    <script>
        Vue.config.productionTip=false;
        var vm = new Vue({
            el: '#app',
            data: {
                    num1:10,
                    num2:20
            },
            methods: {
                Sum(){
                    console.log(this)
                    return (+this.num1)+(+this.num2);
                }
            }
        });
    </script>

  • Get value from computed property

    <div id="app">
        number1:<input type="text" v-model="num1"><br/>
        number2:<input type="text" v-model="num2"><br/>
        <!-- sumResu:<p>{{parseInt(num1)+parseInt(num2)}}</p> -->
        <!-- sumResu:<p>{{Sum()}}</p> -->
        sumResu:<p>{{sumResult}}</p>
       
    </div>

    <script>
        Vue.config.productionTip=false;
        var vm = new Vue({
            el: '#app',
            data: {
                    num1:10,
                    num2:20
            },
            methods: {
                Sum(){
                    console.log(this)
                    return (+this.num1)+(+this.num2);
                }
            },
            computed:{
                sumResult:{
                    get(){
                        console.log(this);
                        return (+this.num1)+(+this.num2);
                    }
                }
            }
        });
    </script>

Summary: Computed properties have a caching mechanism, and the execution will only be triggered when the first execution and the value of the property it depends on changes; it can be abbreviated when the value is not changed.

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.