Trigger and track for manual reactivity in Vue - Cheat Sheet & Quick Revision

Recall & Review

beginner

What does trigger() do in Vue's manual reactivity?

trigger() tells Vue to re-run any effects that depend on a reactive value. It manually signals that the value changed.

beginner

What is the purpose of track() in Vue's manual reactivity system?

track() records which reactive effects depend on a value, so Vue knows what to update when that value changes.

intermediate

Why would you use manual reactivity with track() and trigger() instead of automatic reactivity?

Manual reactivity gives you control to decide exactly when to track dependencies and when to update, useful for custom reactive logic or performance tuning.

intermediate

In Vue, what happens if you call trigger() without calling track() first?

No reactive effects will run because Vue doesn't know which effects depend on the value without track().

beginner

How do track() and trigger() relate to real-life situations?

Think of track() as writing down who needs to be notified about a change, and trigger() as sending the notification when the change happens.

What does track() do in Vue's manual reactivity?

A It records dependencies for reactive updates

B It forces a component to re-render

C It resets reactive state

D It creates a new reactive variable

track() records which reactive effects depend on a value so Vue can update them later.

Which function manually signals Vue to update reactive effects?

A track()

B watch()

C trigger()

D ref()

trigger() tells Vue to re-run effects that depend on a reactive value.

What happens if you call trigger() without track()?

A Reactive state resets

B All effects run twice

C Vue throws an error

D No effects run

Without track(), Vue doesn't know which effects to update, so none run.

Why use manual reactivity with track() and trigger()?

A To control when dependencies are tracked and updated

B To create global variables

C To disable reactivity

D To automatically update all components

Manual reactivity lets you decide exactly when to track and trigger updates.

Which analogy best describes track() and trigger()?

A Writing a letter and mailing it

B Writing down who to notify and sending the notification

C Turning on and off a light switch

D Filling a bucket and emptying it

track() is like noting who to notify, trigger() is sending the notification.

Explain how track() and trigger() work together in Vue's manual reactivity system.

Think about how Vue knows what to update and when.

Describe a real-life example that helps you understand the roles of track() and trigger().

Imagine managing a group of friends to tell about a change.

Practice

1. What is the main purpose of using track and trigger in Vue's manual reactivity system?

easy

A. To handle HTTP requests inside Vue components.

B. To automatically update the UI without any developer intervention.

C. To create new Vue components dynamically.

D. To manually control when Vue updates the UI by tracking dependencies and triggering updates.

Solution

1. Step 1: Understand manual reactivity concept

   Manual reactivity allows developers to decide when Vue should update the UI instead of automatic updates.

2. Step 2: Role of track and trigger

   track watches properties for changes, and trigger notifies Vue to update dependents when changes occur.

3. Final Answer:

   To manually control when Vue updates the UI by tracking dependencies and triggering updates. -> Option D

4. Quick Check:

   Manual reactivity = control updates [OK]

Hint: Remember: track watches, trigger updates UI manually [OK]

Common Mistakes:

• Thinking Vue updates UI automatically without manual triggers
• Confusing track/trigger with component creation
• Assuming track triggers updates directly

2. Which of the following is the correct syntax to import track and trigger from Vue's reactivity package?

easy

A. import { track, trigger } from 'vue';

B. import track, trigger from 'vue';

C. import { track, trigger } from '@vue/reactivity';

D. import * as reactivity from 'vue';

Solution

1. Step 1: Identify correct import source

   The manual reactivity APIs track and trigger are exported from '@vue/reactivity', not directly from 'vue'.

2. Step 2: Correct import syntax

   Using named imports with curly braces is required: import { track, trigger } from '@vue/reactivity';

3. Final Answer:

   import { track, trigger } from '@vue/reactivity'; -> Option C

4. Quick Check:

   Correct import = import { track, trigger } from '@vue/reactivity'; [OK]

Hint: Use curly braces and '@vue/reactivity' for manual reactivity imports [OK]

Common Mistakes:

• Importing from 'vue' instead of '@vue/reactivity'
• Missing curly braces for named imports
• Using default import syntax incorrectly

3. Given the following code snippet, what will be logged to the console?

import { reactive, effect, track, trigger } from '@vue/reactivity';

const state = { count: 0 };

effect(() => {
  track(state, 'count');
  console.log('Count is:', state.count);
});

state.count = 1;
trigger(state, 'count');

medium

A. Count is: 0
Count is: 1

B. Count is: 0

C. Count is: 1

D. No output

Solution

1. Step 1: Initial effect run and tracking

   The effect runs once initially, calling track(state, 'count') and logging 'Count is: 0'.

2. Step 2: State change and manual trigger

   When state.count is set to 1, Vue does not update automatically because manual tracking is used. Calling trigger(state, 'count') manually runs the effect again, logging 'Count is: 1'.

3. Final Answer:

   Count is: 0 Count is: 1 -> Option A

4. Quick Check:

   Manual trigger causes effect rerun [OK]

Hint: Manual trigger reruns effect, so both old and new logged [OK]

Common Mistakes:

• Assuming automatic update without trigger
• Expecting only one log line
• Confusing track with trigger

4. Identify the error in this Vue manual reactivity code snippet:

import { reactive, effect, track, trigger } from '@vue/reactivity';

const state = { value: 10 };

effect(() => {
  track(state.value);
  console.log('Value:', state.value);
});

state.value = 20;
trigger(state, 'value');

medium

A. track is called with a property value instead of the target object and key.

B. trigger is missing after state.value update.

C. effect should not be used with manual reactivity.

D. reactive is not imported correctly.

Solution

1. Step 1: Check track usage

   track requires two arguments: the reactive target object and the property key as a string. Here, track(state.value) passes only the value (number 10), which is incorrect.

2. Step 2: Correct usage of track

   The correct call is track(state, 'value') to track the 'value' property on the reactive object.

3. Final Answer:

   track is called with a property value instead of the target object and key. -> Option A

4. Quick Check:

   track needs (object, key) [OK]

Hint: track needs object and key, not the property value [OK]

Common Mistakes:

• Passing property value instead of object and key to track
• Forgetting to trigger after state change
• Misusing effect with manual reactivity

5. You want to optimize a Vue app by manually controlling reactivity for a large object data. Which approach correctly tracks and triggers updates only for the status property when it changes?

hard

A. Use effect(() => console.log(data.status)) without manual track or trigger.

B. Call track(data, 'status') inside the effect and call trigger(data, 'status') after updating data.status.

C. Call track(data) without property and call trigger(data) after any update.

D. Update data.status and rely on Vue's automatic reactivity without track or trigger.

Solution

1. Step 1: Manual tracking of specific property

   To optimize, track only the 'status' property by calling track(data, 'status') inside the effect watching it.

2. Step 2: Trigger update after changing property

   After updating data.status, call trigger(data, 'status') to notify dependents and update UI.

3. Final Answer:

   Call track(data, 'status') inside the effect and call trigger(data, 'status') after updating data.status. -> Option B

4. Quick Check:

   Track and trigger specific property for manual reactivity [OK]

Hint: Track and trigger only changed property for best performance [OK]

Common Mistakes:

• Tracking or triggering entire object instead of property
• Relying on automatic reactivity when manual control is needed
• Not triggering after property update