Getters for computed store values in Vue - Step-by-Step Execution

Concept Flow - Getters for computed store values

Define Store State

↓

Create Getter: compute value from state

↓

Component uses Getter

↓

Getter returns computed value

↓

Component updates reactively

The flow shows how a store state is defined, a getter computes a value from it, and components use this getter to get reactive computed values.

Execution Sample

Vue

import { defineStore } from 'pinia'

export const useStore = defineStore('main', {
  state: () => ({ count: 2 }),
  getters: {
    doubleCount: (state) => state.count * 2
  }
})

Defines a Pinia store with a state 'count' and a getter 'doubleCount' that returns twice the count.

Execution Table

Step	Action	State.count	Getter doubleCount	Component Output
1	Initialize store	2	Computed as 2 * 2	4
2	Component reads doubleCount	2	4	4 displayed
3	Update state.count = 3	3	Computed as 3 * 2	6
4	Component reacts to getter change	3	6	6 displayed
5	Update state.count = 5	5	Computed as 5 * 2	10
6	Component reacts to getter change	5	10	10 displayed
7	No more updates	5	10	10 displayed

💡 No more state changes; component shows latest computed getter value.

Variable Tracker

Variable	Start	After 1	After 2	After 3	Final
state.count	2	2	3	5	5
getter.doubleCount	4	4	6	10	10
component output	4	4	6	10	10

Key Moments - 2 Insights

Why does the component update automatically when state.count changes?

Because the getter is reactive and computed from state.count, when state.count changes (see execution_table steps 3 and 5), the getter recalculates and triggers the component to update (steps 4 and 6).

Is the getter a function or a value?

The getter acts like a computed property: it is defined as a function but accessed as a value. It recalculates automatically when its dependencies (state.count) change, as shown in the execution_table.

Visual Quiz - 3 Questions

Look at the execution_table at step 3: what is the value of getter.doubleCount?

A 6

B 4

C 3

D 5

💡 Hint

Check the 'Getter doubleCount' column at step 3 in the execution_table.

At which step does the component first display the value 10?

A Step 5

B Step 6

C Step 4

D Step 7

💡 Hint

Look at the 'Component Output' column in the execution_table for when it changes to 10.

If state.count was updated to 4 instead of 3 at step 3, what would getter.doubleCount be then?

A 6

B 4

C 8

D 3

💡 Hint

Remember getter.doubleCount = state.count * 2, see execution_table logic.

Concept Snapshot

Getters in Vue stores compute values from state.
They act like computed properties.
When state changes, getters update automatically.
Components using getters reactively update.
Define getters as functions returning computed values.
Access getters like properties, not functions.

Full Transcript

This visual execution shows how Vue store getters work. First, the store state is defined with a count value. Then a getter called doubleCount computes twice the count. When the component reads doubleCount, it gets the computed value. If the state.count changes, the getter recalculates automatically. The component updates reactively to show the new computed value. This flow helps beginners see how getters provide reactive computed values from store state in Vue.

Practice

1. What is the main purpose of getters in a Vue store?

easy

A. To compute and return derived state based on the store's data

B. To directly modify the store's state values

C. To register new components in the Vue app

D. To handle user input events in components

Solution

1. Step 1: Understand what getters do

   Getters compute values derived from the store's state without changing the state itself.

2. Step 2: Compare options with this role

   Only To compute and return derived state based on the store's data describes computing and returning derived state, which matches getters' purpose.

3. Final Answer:

   To compute and return derived state based on the store's data -> Option A

4. Quick Check:

   Getters compute derived state = B [OK]

Hint: Getters compute data, mutations change data [OK]

Common Mistakes:

• Confusing getters with mutations that modify state
• Thinking getters handle events or components
• Assuming getters register components

2. Which of the following is the correct syntax to define a getter named completedTasks in a Vue store?

easy

A. getters: { completedTasks: function() { return state.tasks.filter(t => t.done) } }

B. getters: { completedTasks: (state) => state.tasks.filter(t => t.done) }

C. getters: { completedTasks() { return this.tasks.filter(t => t.done) } }

D. getters: { completedTasks: (state) => { state.tasks.filter(t => t.done) } }

Solution

1. Step 1: Review correct getter syntax

   A getter is a function receiving state and returning a value. Arrow function with implicit return is common.

2. Step 2: Check each option

   getters: { completedTasks: (state) => state.tasks.filter(t => t.done) } correctly uses an arrow function with state parameter and returns filtered tasks. getters: { completedTasks() { return this.tasks.filter(t => t.done) } } incorrectly uses this which is not available. getters: { completedTasks: function() { return state.tasks.filter(t => t.done) } } lacks state parameter. getters: { completedTasks: (state) => { state.tasks.filter(t => t.done) } } misses return statement.

3. Final Answer:

   getters: { completedTasks: (state) => state.tasks.filter(t => t.done) } -> Option B

4. Quick Check:

   Getter syntax needs state param and return value = C [OK]

Hint: Getters get state as first param and return computed value [OK]

Common Mistakes:

• Using this inside getters instead of state
• Forgetting to return a value from the getter
• Not including state as a parameter

3. Given the Vue store state:

state: { items: [ { id: 1, done: true }, { id: 2, done: false } ] }

and getter:

getters: { doneCount: (state) => state.items.filter(i => i.done).length }

What will store.getters.doneCount return?

medium

A. 2

B. undefined

C. 1

D. 0

Solution

1. Step 1: Analyze the state array

   There are two items: one with done: true and one with done: false.

2. Step 2: Evaluate the getter logic

   The getter filters items where done is true, so only one item matches. Then it returns the length, which is 1.

3. Final Answer:

   1 -> Option C

4. Quick Check:

   Count of done items = 1 [OK]

Hint: Count items with done true using filter and length [OK]

Common Mistakes:

• Counting all items instead of filtered ones
• Returning the filtered array instead of its length
• Assuming undefined because of missing return

4. Identify the error in this Vue store getter definition:

getters: { activeUsers: (state) => { state.users.filter(u => u.active) } }

medium

A. Filter method cannot be used on arrays

B. Incorrect parameter name; should be 'context' instead of 'state'

C. Using arrow function is not allowed for getters

D. Missing return statement inside the getter function

Solution

1. Step 1: Check getter function body

   The getter uses curly braces but does not return the filtered array explicitly.

2. Step 2: Understand arrow function return rules

   When using curly braces in arrow functions, you must use return to output a value. Without it, the function returns undefined.

3. Final Answer:

   Missing return statement inside the getter function -> Option D

4. Quick Check:

   Arrow function with braces needs explicit return = A [OK]

Hint: Arrow functions with braces need explicit return [OK]

Common Mistakes:

• Assuming implicit return with curly braces
• Confusing parameter names for getters
• Thinking filter can't be used on arrays

5. You want a getter that returns the total price of items in a cart, but only for items with quantity > 0.
Given state:

state: { cart: [ { price: 10, quantity: 2 }, { price: 5 }, { price: 3, quantity: 4 } ] }

Which getter correctly computes this total?

hard

A. totalPrice: (state) => state.cart.filter(i => i.quantity > 0).reduce((sum, item) => sum + item.price * item.quantity, 0)

B. totalPrice: (state) => state.cart.reduce((sum, item) => sum + item.price * item.quantity, 0)

C. totalPrice: (state) => state.cart.map(i => i.price * i.quantity).reduce((a, b) => a + b)

D. totalPrice: (state) => state.cart.reduce((sum, item) => sum + item.price, 0)

Solution

1. Step 1: Understand the requirement

   Only items with quantity > 0 should be counted in total price calculation.

2. Step 2: Analyze each option

   totalPrice: (state) => state.cart.reduce((sum, item) => sum + item.price * item.quantity, 0) sums all items regardless of quantity. totalPrice: (state) => state.cart.filter(i => i.quantity > 0).reduce((sum, item) => sum + item.price * item.quantity, 0) filters items with quantity > 0 before summing, which is correct. totalPrice: (state) => state.cart.map(i => i.price * i.quantity).reduce((a, b) => a + b) sums all items including those with zero quantity. totalPrice: (state) => state.cart.reduce((sum, item) => sum + item.price, 0) sums only prices ignoring quantity.

3. Final Answer:

   totalPrice: (state) => state.cart.filter(i => i.quantity > 0).reduce((sum, item) => sum + item.price * item.quantity, 0) -> Option A

4. Quick Check:

   Filter then reduce for quantity > 0 total = A [OK]

Hint: Filter items with quantity > 0 before summing [OK]

Common Mistakes:

• Not filtering out items with zero quantity
• Summing prices without multiplying by quantity
• Using map without filtering first