{{fullName}} There is also the idea that if you only use getters in Vuex, you’ll never accidentally try to set the value. Access the store directly. This isn't everyone's cup of tea, but it works well for smaller components that don't use too many getters, mutations or actions. Like computed properties, a getter's result is cached based on its dependencies, and will only re-evaluate when some of its dependencies have changed. Luckily, Vuex comes with two methods that help us in this case. Subscribe to my email list now at https://thewebdev.info/subscribe/. This is particularly useful if you want to query your store. In this Vue.js tutorial, we’ll look into how we can use higher order functions to create dynamic getters in Vuex. Let’s say that we aren’t able to use the function or helper syntax at all. For instance, if we want to make a getter that gets a todo by ID, we can write the following: Then we see todo1 displayed on the screen. If we take a look at our main.js file, we see we’re importing our Vuex store file, and providing it to our root Vue instance. Vuex getters behave a lot like Mongoose getters: they're special properties that are computed from Usage.