This time I will bring you a detailed explanation of vue computed properties. What are theprecautionswhen using vue computed properties. The following is a practical case, let’s take a look.
1. What is a computed attribute
Expressionswithin templates are very convenient, but they were originally designed for simple operations. Putting too much logic into a template can make it overweight and difficult to maintain. For example:
{{ message.split('').reverse().join('') }}
The expression here contains 3 operations, which is not very clear, so when you encounter complex logic, you should use Vue's special calculated attribute computed to handle it.
2. Usage of computed properties
Various complex logic can be completed in a calculated attribute, including operations, function calls, etc., as long as a result is returned in the end.
Let’s rewrite the above example using computed properties
Original message: "{{ message }}"
Computed reversed message: "{{ reversedMessage }}"
//我们把复杂处理放在了计算属性里面了 var vm = new Vue({ el: '#example', data: { message: 'Hello' }, computed: { reversedMessage: function () { // `this` 指向 vm 实例 return this.message.split('').reverse().join('') } } });
result:
Original message: "Hello"
Computed reversed message: "olleH"
In addition to the simple usage in the above example, calculated properties can also rely on the data of multiple Vue instances. As long as any of the data changes, the calculated properties will be re-executed and the view will be updated.
总价为:{{price}}
var app = new Vue({ el: '#app', data: { package1: { count: 5, price: 5 }, package2: { count: 10, price: 10 } }, computed: { price: function(){ return this.package1.count*this.package1.price+this.package2.count*this.package2.price //总价随着货物或价格的改变会重新计算 } }, methods: { //对象的方法 add: function(){ this.package1.count++ } } });
There are two very practical tips for calculated properties that are easily overlooked: first, calculated properties can depend on other calculated properties; second, calculated properties can not only rely on the data of the current Vue instance, but also rely on the data of other instances, for example:
{{ reverseText}}
var app1 = new Vue({ el: '#app1', data: { text: 'computed' } }); var app2 = new Vue({ el: '#app2', computed: { reverseText: function(){ return app1.text.split('').reverse().join(''); //使用app1的数据进行计算 } } });
Each calculated property contains a getter and a setter. Our two examples above are the default usage of calculated properties, only using getters to read.
When you need it, you can also provide a setter function. When you manually modify the value of a calculated property just like modifying ordinary data, the setter function will be triggered to perform some custom operations, such as:
var vm = new Vue({ el: '#demo', data: { firstName: 'Foo', lastName: 'Bar' }, computed: { fullName: { // getter get: function () { return this.firstName + ' ' + this.lastName }, // setter set: function (newValue) { var names = newValue.split(' '); this.firstName = names[0]; this.lastName = names[names.length - 1]; } } } }); //现在再运行 vm.fullName = 'John Doe' 时,setter 会被调用,vm.firstName 和 vm.lastName 也会相应地被更新。
In most cases, we will only use the default getter method to read a calculated property. Setters are rarely used in business, so when declaring a calculated property, you can directly use the default writing method without having to combine getter and setter. All declared.
3. Calculated attribute cache
In the above example, in addition to using calculated properties, we can also achieve the same effect by calling methods in expressions, such as:
{{reverseTitle()}}
// 在组件中 methods: { reverseTitle: function () { return this.title.split('').reverse().join('') } }
We could define the same function as a method instead of a computed property, and the end result would indeed be exactly the same either way. Just one usesreverseTitle()
to get the value, and the other uses reverseTitle to get the value.
However, the difference is that computed properties are cached based on their dependencies. A computed property is only re-evaluated when its associated dependencies change.
This means that as long as the title has not changed, accessing the reverseTitle calculated property multiple times will immediately return the previous calculation result without having to execute the function again.
A small example:
{{reverseTitle}}
{{reverseTitle1()}}
总价为:{{price}}
computed: { reverseTitle: function(){ return this.title.split('').reverse().join('') //而使用计算属性,只要title没变,页面渲染是不会重新进这里来计算的,而是使用了缓存。 }, price: function(){ return this.package1.count*this.package1.price+this.package2.count*this.package2.price } }, methods: { //对象的方法 add: function(){ this.package1.count++ }, reverseTitle1: function(){ return this.title.split('').reverse().join('') //点击补充货物,也会进这个方法,再次计算。不是刷新,而是只要页面渲染,就会进方法里重新计算。 } },
In contrast, the calling method will always execute the function again whenever a rerender is triggered.
Why do we need caching? Suppose we have a computationally expensive property A, which requires traversing a huge array and doing a lot of calculations. Then we might have other computed properties that depend on A .
Without caching, we would inevitably execute A's getter multiple times! If you don't want caching, use methods instead.
Let’s take a look at the use of Vue calculated properties
I believe you have mastered the method after reading the case in this article. For more exciting information, please pay attention to other related articles on the PHP Chinese website!
Recommended reading:
##Detailed explanation of webpack’s mobile-side automated build rem method
The above is the detailed content of Detailed explanation of vue computed properties. For more information, please follow other related articles on the PHP Chinese website!