Store-to-store interaction in Vue - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is store-to-store interaction in Vue?

Store-to-store interaction means sharing or syncing data between different Vue stores so they can work together smoothly.

intermediate

How can one Vue store access data from another store?

One store can import the other store and use its state or actions directly inside its own functions.

intermediate

Why use store-to-store interaction instead of putting all data in one store?

Splitting stores keeps code organized and easier to manage, especially in big apps, while still allowing stores to share data when needed.

advanced

What Vue feature helps to reactively watch changes in another store's state?

Vue's watch function can watch state from another store and react when it changes.

advanced

Give an example of a simple store-to-store interaction in Vue.

Store A imports Store B and calls Store B's action to update data. Store A can also watch Store B's state to react to changes.

What is the main reason to use store-to-store interaction in Vue?

A To disable reactivity

B To share data between different stores

C To avoid using Vue components

D To create multiple Vue apps

Store-to-store interaction is used to share or sync data between different Vue stores.

How do you access another store inside a Vue store?

A Call Vue.component()

B Use global variables

C Import the other store and use its state or actions

D Use CSS selectors

You import the other store module and then use its state or actions inside your store.

Which Vue function helps react to changes in another store's state?

A watch

B computed

C mounted

D provide

The watch function lets you react when a value changes, including state from another store.

Why might you split data into multiple stores instead of one big store?

A To slow down the app

B To disable reactivity

C To avoid using Vue Router

D To keep code organized and manageable

Splitting stores helps keep code clean and easier to maintain.

What is a common pattern for store-to-store interaction?

A One store imports another and calls its actions or watches its state

B Stores communicate only through events

C Stores never share data

D Stores use CSS to interact

A common pattern is importing one store into another to share data or trigger actions.

Explain how two Vue stores can share data and keep it in sync.

Think about how one store can use another store's state and actions.

Describe why splitting your app's data into multiple stores can be helpful and how they can still interact.

Consider the benefits of smaller stores and how they communicate.

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