All language subtitles for 016 Understanding Getters_en

In the previous lecture, we learned about mutations there a way to change a state property inside the

store.

Just like you can create mutations, you can create something called getters.

Getters are exactly what they sound like.

They allow you to access a state property from the store.

Using a getter is optional.

We can access the state property directly through the store object.

The store object is injected into every component.

Here's an example of how you would access the state.

This is one way of grabbing a state property from the store.

Peneha offers another solution for retrieving a state property called Getters.

The main benefit of using a getter is the support for caching.

It can intelligently update itself when the state changes.

We've learned that the computed properties are one way to cache a value.

One solution might be to write a computed property for every state property we'd like to use in a given

component that would work.

But then we would face duplication issues.

We'd have to define the same computed properties in every component.

That's where getters come in.

You can think of getters as computed properties for your store.

One of the main benefits of a getter is that they're accessible to all components.

Define a getter once, use it everywhere.

Getters are also smart.

They will only update if the state changes.

This can help with the performance of an application.

Let's prepare our application for using a getter in the next lecture.