Store-to-store interaction in Vue - Step-by-Step Execution

Concept Flow - Store-to-store interaction

Store A updates state

↓

Store A triggers event or exposes getter

↓

Store B listens or accesses Store A

↓

Store B updates its own state based on Store A

↓

Components using Store B react to changes

This flow shows how one Vue store updates its state, which then influences another store's state, enabling reactive data sharing.

Execution Sample

Vue

import { defineStore } from 'pinia';
import { computed } from 'vue';

export const useStoreA = defineStore('storeA', {
  state: () => ({ count: 0 }),
  actions: { increment() { this.count++ } }
});

export const useStoreB = defineStore('storeB', () => {
  const storeA = useStoreA();
  const doubleCount = computed(() => storeA.count * 2);
  return { doubleCount };
});

Store A has a count and an increment action; Store B reads Store A's count and computes doubleCount reactively.

Execution Table

Step	Action	Store A count	Store B doubleCount	Effect
1	Initialize Store A and Store B	0	0	Stores created, doubleCount = 0
2	Call storeA.increment()	1	2	count increments, doubleCount updates reactively
3	Call storeA.increment() again	2	4	count increments, doubleCount updates reactively
4	No further actions	2	4	State stable, no changes

💡 No more actions; reactive updates keep Store B in sync with Store A

Variable Tracker

Variable	Start	After 1	After 2	Final
storeA.count	0	1	2	2
storeB.doubleCount	0	2	4	4

Key Moments - 2 Insights

Why does storeB.doubleCount update automatically when storeA.count changes?

Because storeB.doubleCount is a computed property depending on storeA.count, Vue's reactivity system updates it automatically as shown in execution_table rows 2 and 3.

Can storeB change storeA's count directly?

No, storeB only reads storeA's state; to change storeA's count, you must call storeA's actions like increment(), as shown in step 2.

Visual Quiz - 3 Questions

Look at the execution table, what is storeB.doubleCount after the first increment?

A 0

B 1

C 2

D 4

💡 Hint

Check row 2 under storeB.doubleCount in the execution_table

At which step does storeA.count become 2?

A Step 3

B Step 1

C Step 2

D Step 4

💡 Hint

Look at storeA.count values in execution_table rows

If storeA.increment() was not called, what would storeB.doubleCount be at step 3?

A 4

B 0

C 2

D Undefined

💡 Hint

Refer to variable_tracker and execution_table initial values

Concept Snapshot

Store-to-store interaction in Vue with Pinia:
- Store A holds state and actions.
- Store B imports Store A and uses its state.
- Store B uses computed properties to react to Store A changes.
- Changes in Store A trigger reactive updates in Store B.
- Components using Store B see updated values automatically.

Full Transcript

This example shows how two Vue stores interact using Pinia. Store A has a count state and an increment action. Store B imports Store A and defines a computed property doubleCount that doubles Store A's count. When storeA.increment() is called, storeA.count increases, and storeB.doubleCount updates automatically due to Vue's reactivity. The execution table traces these changes step-by-step, showing how state flows from Store A to Store B. Key moments clarify why computed properties update and that Store B cannot directly modify Store A's state. The visual quiz tests understanding of these reactive updates and state changes.

Practice

1. What is the main purpose of store-to-store interaction in Vue's Pinia stores?

easy

A. To create multiple independent stores without any connection

B. To allow one store to access or call actions from another store

C. To replace Vue components with stores

D. To automatically sync stores with a backend database

Solution

1. Step 1: Understand store-to-store interaction

   Store-to-store interaction means one store can use another store's state or actions to share data or trigger updates.

2. Step 2: Identify the purpose

   This interaction helps keep data consistent by letting stores communicate, not by replacing components or syncing automatically.

3. Final Answer:

   To allow one store to access or call actions from another store -> Option B

4. Quick Check:

   Store-to-store interaction = Access other store's actions/state [OK]

Hint: Remember: stores talk by calling each other's actions [OK]

Common Mistakes:

• Thinking stores replace components
• Assuming stores sync automatically with backend
• Believing stores are always independent

2. Which of the following is the correct way to use one Pinia store inside another in Vue 3?

easy

A. const storeA = useStoreA(); const storeB = useStoreB(); import { useStoreA } from './storeA';

B. import useStoreA from './storeA'; const storeB = useStoreB();

C. const storeA = useStoreB(); const storeB = useStoreA();

D. import { useStoreA } from './storeA'; const storeB = useStoreB(); const storeA = useStoreA();

Solution

1. Step 1: Import the store function before usage

   You must import the store function (e.g., useStoreA) before calling it to get the store instance.

2. Step 2: Call the store functions to get instances

   Call useStoreA() and useStoreB() to get their store instances for interaction.

3. Final Answer:

   import { useStoreA } from './storeA'; const storeB = useStoreB(); const storeA = useStoreA(); -> Option D

4. Quick Check:

   Import then call stores = correct syntax [OK]

Hint: Always import store before calling useStore() [OK]

Common Mistakes:

• Calling useStore before importing
• Mixing store names when calling
• Incorrect import syntax without braces

3. Given these two Pinia stores, what will be the console output after calling storeB.incrementA()?

const useStoreA = defineStore('A', {
  state: () => ({ count: 0 }),
  actions: { increment() { this.count++ } }
});

const useStoreB = defineStore('B', {
  actions: {
    incrementA() {
      const storeA = useStoreA();
      storeA.increment();
      console.log(storeA.count);
    }
  }
});

const storeB = useStoreB();
storeB.incrementA();

medium

A. 1

B. 0

C. undefined

D. Error: useStoreA is not defined

Solution

1. Step 1: Understand storeA initial state and increment

   storeA starts with count = 0. Calling increment() increases count by 1.

2. Step 2: Trace incrementA action in storeB

   incrementA calls storeA.increment(), then logs storeA.count which is now 1.

3. Final Answer:

   1 -> Option A

4. Quick Check:

   Increment count from 0 to 1, then log 1 [OK]

Hint: Calling other store's action updates its state immediately [OK]

Common Mistakes:

• Assuming count stays 0 after increment
• Thinking console logs undefined
• Forgetting to call useStoreA inside action

4. What is wrong with this code snippet trying to use storeA inside storeB?

const useStoreA = defineStore('A', {
  state: () => ({ value: 10 })
});

const useStoreB = defineStore('B', {
  actions: {
    updateValue() {
      const storeA = useStoreA;
      storeA.value = 20;
    }
  }
});

medium

A. defineStore cannot be used inside actions

B. Cannot assign value directly to storeA.value

C. useStoreA is not called as a function, so storeA is not a store instance

D. State must be a function returning an object

Solution

1. Step 1: Check how useStoreA is used inside updateValue

   useStoreA is referenced without parentheses, so storeA is a function reference, not a store instance.

2. Step 2: Understand consequences of missing parentheses

   Without calling useStoreA(), you cannot access or modify state like storeA.value.

3. Final Answer:

   useStoreA is not called as a function, so storeA is not a store instance -> Option C

4. Quick Check:

   Call useStoreA() to get store instance [OK]

Hint: Always call useStore() with () to get the store [OK]

Common Mistakes:

• Forgetting parentheses when calling useStore
• Trying to assign state directly without actions
• Misunderstanding defineStore usage

5. You have two stores: useCartStore managing cart items and useUserStore managing user info. You want to clear the cart when the user logs out. How should you implement this store-to-store interaction inside useUserStore?

hard

A. Inside the logout action, call const cart = useCartStore(); cart.clearItems();

B. Emit an event from useUserStore and listen in useCartStore to clear items

C. Directly modify useCartStore state without calling its actions

D. Reset useUserStore state and expect useCartStore to reset automatically

Solution

1. Step 1: Identify the correct way to trigger cart clearing

   Calling useCartStore() inside useUserStore's logout action gets the cart store instance.

2. Step 2: Use cart store's action to clear items

   Calling cart.clearItems() properly updates the cart state in a controlled way.

3. Final Answer:

   Inside the logout action, call const cart = useCartStore(); cart.clearItems(); -> Option A

4. Quick Check:

   Call other store's action inside logout to clear cart [OK]

Hint: Call other store's action inside your store's action [OK]

Common Mistakes:

• Trying to modify other store's state directly
• Using events instead of direct store calls
• Expecting automatic reset without explicit calls