Trigger and track for manual reactivity in Vue - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create a reactive reference in Vue.

Vue

const count = [1](0);

Drag options to blanks, or click blank then click option'

Aref

Bcomputed

Creactive

Dwatch

Attempts:

3 left

💡 Hint

Common Mistakes

Using reactive instead of ref for primitive values.

Use ref to create a reactive reference for a primitive value like a number.

2fill in blank

medium

Complete the code to manually trigger reactivity on a ref.

Vue

import { ref, [1] } from 'vue';

const state = ref({ count: 0 });

[1](state);

Drag options to blanks, or click blank then click option'

AtriggerRef

BtoRefs

CmarkRaw

DshallowReactive

Attempts:

3 left

💡 Hint

Common Mistakes

Using toRefs or markRaw instead of triggerRef.

triggerRef is used to manually trigger reactivity on a ref.

3fill in blank

hard

Fix the error in the code to track manual reactivity correctly.

Vue

import { ref, [1] } from 'vue';

const state = ref({ count: 0 });

function increment() {
  [1](state);
  state.value.count++;
}

Drag options to blanks, or click blank then click option'

AwatchEffect

BtriggerRef

CmarkRaw

DtrackRef

Attempts:

3 left

💡 Hint

Common Mistakes

Using triggerRef instead of trackRef for tracking.

trackRef is used to track manual reactivity dependencies, which is missing here.

4fill in blank

hard

Fill both blanks to create a ref and manually trigger its update.

Vue

import { [1], [2] } from 'vue';

const state = [1]({ count: 0 });

function update() {
  state.value.count++;
  [2](state);
}

Drag options to blanks, or click blank then click option'

Areactive

BtriggerRef

Cref

Dwatch

Attempts:

3 left

💡 Hint

Common Mistakes

Using reactive instead of ref for the object.

Use ref to create the ref and triggerRef to manually trigger updates.

5fill in blank

hard

Fill all three blanks to track and trigger manual reactivity on a ref.

Vue

import { [1], [2], [3] } from 'vue';

const count = [1](0);

function manualUpdate() {
  [2](count);
  count.value++;
  [3](count);
}

Drag options to blanks, or click blank then click option'

Aref

BtrackRef

CtriggerRef

Dreactive

Attempts:

3 left

💡 Hint

Common Mistakes

Using reactive instead of ref for primitive values.

Create a ref with ref, track dependencies with trackRef, and trigger updates with triggerRef.

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