{"componentChunkName":"component---src-templates-blog-post-js","path":"/computed-properties-what-are-they/","webpackCompilationHash":"23268da9a2d41a689f81","result":{"data":{"site":{"siteMetadata":{"title":"A Vue Blog","author":"Gautham Lal"}},"markdownRemark":{"id":"f8ebd120-fb94-5b46-b00b-c914efcbf946","excerpt":"Let’s go back to the very first blog post where we talked about templates. Another useful thing about templates is that you can write simple JavaScript…","html":"

Let’s go back to the very first blog post where we talked about templates. Another useful thing about templates is that you can write simple JavaScript expressions in them.

\n
<div>{{ count * 10 }}</div>
\n

While this is extremely useful, they are limited to single expressions. And when they tend to get long, the code gets bloated and can be tough to read. And in case you need to repeat the same at multiple places, it leads to repetitive code.

\n

In comes the computed property to save the day. Let’s look at an example.

\n
<div id=\"app\">{{ getFullName }}</div>
\n
let app = new Vue({\n  el: '#app',\n  data: {\n    firstName: 'Light',\n    lastName: 'Yagami',\n  },\n  computed: {\n    getFullName: function() {\n      return this.firstName + ' ' + this.lastName;\n    }\n  }\n});
\n

And we get the full name printed! Now whenever you change the value of the data properties being used inside the getFullName computed property, it returns a new full name. So if you go ahead and make a change like app.lastName = “Kira”, a new full name ‘Light Kira’ gets printed!

\n

Computed vs Methods

\n

You must have noticed we could’ve received the same result by using methods.

\n

To begin with, although computed properties are functions at the end of the day, we didn’t have to call them by getFullName(), like methods. We can call them the same way we do with data properties.

\n

Although the end results are the same, the way computed and method properties get there are different. Computed properties are cached. What it means is that the result of a computed property is internally cached and is re-evaluated only when a reactive source gets updated. This means as long as firstName and lastName remains the same, subsequent calls to getFullName does not cause a re-execution of the function and in turn returns the previously calculated cached result.

\n

It is also important to note that the dependant property has to be reactive. Hence the following will not cause a re-render.

\n
computed: {\n  nowDate: function() {\n    return Date.now();\n  }\n}
\n

It will render once and will not update on subsequent re-renders.

\n

A huge upside of using computed over methods is the caching. In a case where we have a huge computed property with a lot of computations, execution of computed property on every re-render even when the data source hasn’t changed can be expensive. Computed property lets us skip this by caching the result and returning the same till a re-execution is needed.

\n

But that’s not all! In the next post, we have another property to look out for. Or should I say, watch out for?

\n

Until next time, bye!

","frontmatter":{"title":"Computed Properties, What Are They?","date":"August 21, 2019","description":"While methods are useful, we have an alternative that can be more efficient. Computed Properties."}}},"pageContext":{"isCreatedByStatefulCreatePages":false,"slug":"/computed-properties-what-are-they/","previous":{"fields":{"slug":"/methods-in-vue.js/"},"frontmatter":{"title":"Methods in Vue.js"}},"next":{"fields":{"slug":"/watchers-to-watch-your-properties/"},"frontmatter":{"title":"Watchers, to Watch Your Properties!"}}}}}