Trigger and track for manual reactivity in Vue - Mini Project: Build & Apply

Trigger and Track for Manual Reactivity in Vue

📖 Scenario: You are building a simple Vue app that tracks a counter value. You want to manually control when Vue updates the UI by triggering and tracking reactivity yourself.

🎯 Goal: Create a Vue component that uses trigger and track functions from Vue's reactivity system to manually update the UI when a button is clicked.

📋 What You'll Learn

Create a reactive object with a count property initialized to 0

Create a track function call to track the count property

Create a trigger function call to trigger updates when count changes

Add a button that increments count and triggers the update manually

Display the current count value in the template

💡 Why This Matters

🌍 Real World

Manual reactivity control is useful when you want to optimize performance by controlling exactly when Vue updates the UI, such as in complex animations or large data sets.

💼 Career

Understanding manual reactivity helps frontend developers optimize Vue apps and debug reactivity issues, a valuable skill in professional Vue development.

1

Setup reactive state with count

Create a reactive object called state with a property count set to 0 using Vue's reactive function.

Vue

import { reactive } from 'vue'

export default {
  setup() {
    // Create reactive state object with count = 0
  }
}

Hint

Use reactive from Vue to create an object with count set to 0.

2

Import and setup track and trigger

Import track and trigger from 'vue' and create a trackCount function that calls track(state, 'count').

Vue

import { reactive, track, trigger } from 'vue'

export default {
  setup() {
    const state = reactive({ count: 0 })
    // Create trackCount function to track state.count
  }
}

Hint

Import track and trigger and create a function that calls track(state, 'count').

3

Create increment function to update and trigger

Create an increment function that increases state.count by 1 and calls trigger(state, 'count') to manually update the UI.

Vue

import { reactive, track, trigger } from 'vue'

export default {
  setup() {
    const state = reactive({ count: 0 })
    function trackCount() {
      track(state, 'count')
    }
    // Create increment function to increase count and trigger update
  }
}

Hint

Create a function that increases state.count and calls trigger(state, 'count') to update.

4

Add template to display count and button to increment

Add a template that calls trackCount() to track count, displays state.count, and includes a button that calls increment when clicked.

Vue

  
  
  



import { reactive, track, trigger } from 'vue'

const state = reactive({ count: 0 })
function trackCount() {
  track(state, 'count')
}
function increment() {
  state.count++
  trigger(state, 'count')
}

Hint

Use {{ trackCount(); state.count }} in the template to track and display count, and add a button with @click="increment".

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