Triggering detection manually in Angular - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ component_behavior

intermediate

What happens when ChangeDetectorRef.detectChanges() is called?

Consider an Angular component where you manually call detectChanges() from ChangeDetectorRef. What is the immediate effect on the component's view?

Angular

import { Component, ChangeDetectorRef } from '@angular/core';

@Component({
  selector: 'app-manual-detect',
  template: `<p>{{counter}}</p><button (click)="increment()">Increment</button>`
})
export class ManualDetectComponent {
  counter = 0;
  constructor(private cdr: ChangeDetectorRef) {}
  increment() {
    this.counter++;
    this.cdr.detectChanges();
  }
}

A The component's view updates only after Angular's next automatic change detection cycle.

B The component's view updates immediately to reflect the new counter value.

C The component's view does not update until the component is destroyed and recreated.

D Calling detectChanges() causes an error because it cannot be called manually.

💡 Hint

Think about what detectChanges() does in Angular's change detection mechanism.

Calling detectChanges() triggers Angular to check the component and its children immediately, updating the view to reflect any changes in data bindings.

❓ lifecycle

intermediate

When should you use ApplicationRef.tick() in Angular?

Which scenario correctly describes when to use ApplicationRef.tick() to trigger change detection manually?

A When you want to reset the component's state to initial values.

B When you want to detect changes only in a single component and its children.

C When you want to trigger change detection for the entire application immediately.

D When you want to stop Angular's automatic change detection.

💡 Hint

ApplicationRef.tick() affects the whole app, not just one component.

ApplicationRef.tick() triggers change detection for the entire Angular application immediately, useful in rare cases when you need a full manual check.

🔧 Debug

advanced

Why does calling detectChanges() inside ngAfterViewInit cause ExpressionChangedAfterItHasBeenCheckedError?

Given this Angular component code, why does calling detectChanges() inside ngAfterViewInit cause an ExpressionChangedAfterItHasBeenCheckedError?

Angular

import { Component, ChangeDetectorRef, AfterViewInit } from '@angular/core';

@Component({
  selector: 'app-error-demo',
  template: `<p>{{message}}</p>`
})
export class ErrorDemoComponent implements AfterViewInit {
  message = 'Initial';
  constructor(private cdr: ChangeDetectorRef) {}
  ngAfterViewInit() {
    this.message = 'Changed after view init';
    this.cdr.detectChanges();
  }
}

A Because the view was already checked and changing data after that triggers the error.

B Because ngAfterViewInit runs before the component is initialized.

C Because message is not a valid property to bind in the template.

D Because detectChanges() cannot be called inside lifecycle hooks.

💡 Hint

Think about Angular's change detection timing and when it expects data to be stable.

The error occurs because Angular detects that a bound value changed after it finished checking the view, which is not allowed to prevent inconsistent UI.

📝 Syntax

advanced

Which code snippet correctly injects ChangeDetectorRef and triggers manual detection?

Select the code snippet that correctly injects ChangeDetectorRef and triggers manual change detection in an Angular component method.

A

constructor(private cdr: ChangeDetectorRef) {}

update() {
  this.cdr.tick();
}

B

constructor(cdr: ChangeDetectorRef) {}

update() {
  cdr.detectChanges();
}

C

constructor(private cdr: ChangeDetectorRef) {}

update() {
  ChangeDetectorRef.detectChanges();
}

D

constructor(private cdr: ChangeDetectorRef) {}

update() {
  this.cdr.detectChanges();
}

💡 Hint

Remember how to use dependency injection and call instance methods.

Option D correctly injects ChangeDetectorRef as a private property and calls detectChanges() on that instance.

❓ state_output

expert

What is the output after manually detaching and reattaching change detection?

Given this Angular component code, what will be the displayed counter value after clicking the button twice?

Angular

import { Component, ChangeDetectorRef } from '@angular/core';

@Component({
  selector: 'app-detach-demo',
  template: `<p>{{counter}}</p><button (click)="increment()">Increment</button>`
})
export class DetachDemoComponent {
  counter = 0;
  constructor(private cdr: ChangeDetectorRef) {
    this.cdr.detach();
  }
  increment() {
    this.counter++;
    if (this.counter === 2) {
      this.cdr.reattach();
    }
  }
}

A After two clicks, the displayed counter jumps directly to 2 without showing 1.

B The displayed counter updates immediately on every click.

C The displayed counter never updates because change detection is detached.

D After two clicks, the displayed counter is 1, then updates to 2 after reattach.

💡 Hint

Consider what happens when change detection is detached and then reattached.

Initially, change detection is detached, so the view does not update on the first click (counter=1). After the second click, reattach() is called, so the view updates to show 2.

Practice

1. What is the main purpose of ChangeDetectorRef.detectChanges() in Angular?

easy

A. To reset the component's state to its initial value.

B. To stop Angular from detecting any changes in the component.

C. To automatically refresh the entire application.

D. To manually trigger Angular's change detection and update the view.

Solution

1. Step 1: Understand Angular's change detection

   Angular normally updates the view automatically when data changes inside its flow.

2. Step 2: Role of detectChanges()

   When changes happen outside Angular's flow, detectChanges() forces Angular to check and update the view manually.

3. Final Answer:

   To manually trigger Angular's change detection and update the view. -> Option D

4. Quick Check:

   Manual change detection = detectChanges() [OK]

Hint: detectChanges() forces Angular to update view manually [OK]

Common Mistakes:

• Thinking detectChanges() stops change detection
• Confusing detectChanges() with resetting component state
• Assuming detectChanges() refreshes the whole app

2. Which of the following is the correct way to inject ChangeDetectorRef in an Angular component constructor?

easy

A. constructor(private cd: ChangeDetectorRef()) {}

B. constructor(cd: ChangeDetectorRef) {}

C. constructor(private cd: ChangeDetectorRef) {}

D. constructor(private cd = new ChangeDetectorRef()) {}

Solution

1. Step 1: Understand Angular dependency injection syntax

   Angular injects services by declaring them as private/public in the constructor parameters.

2. Step 2: Correct syntax for ChangeDetectorRef injection

   Using private cd: ChangeDetectorRef tells Angular to inject the service automatically.

3. Final Answer:

   constructor(private cd: ChangeDetectorRef) {} -> Option C

4. Quick Check:

   Inject with private and type only [OK]

Hint: Inject services with private and type in constructor [OK]

Common Mistakes:

• Calling ChangeDetectorRef as a function
• Manually creating new ChangeDetectorRef instance
• Omitting private/public keyword

3. Given this Angular component snippet:

import { ChangeDetectorRef } from '@angular/core';

@Component({ selector: 'app-demo', template: '{{counter}}' })
export class DemoComponent {
  counter = 0;
  constructor(private cd: ChangeDetectorRef) {}

  increment() {
    setTimeout(() => {
      this.counter++;
      this.cd.detectChanges();
    }, 1000);
  }
}

What will be displayed after calling increment()?

medium

A. The counter will update to 1 after 1 second.

B. The counter will stay at 0 and never update.

C. The counter will update immediately without delay.

D. The app will throw a runtime error.

Solution

1. Step 1: Analyze the setTimeout callback

   After 1 second, counter increments by 1 inside the callback.

2. Step 2: Understand detectChanges() effect

   Calling detectChanges() manually triggers Angular to update the view with the new counter value.

3. Final Answer:

   The counter will update to 1 after 1 second. -> Option A

4. Quick Check:

   Manual detectChanges() updates view after async change [OK]

Hint: detectChanges() updates view after async changes [OK]

Common Mistakes:

• Assuming view updates immediately without detectChanges()
• Thinking setTimeout blocks UI
• Expecting error due to async code

4. Consider this Angular code snippet:

constructor(private cd: ChangeDetectorRef) {}

updateData() {
  this.data = fetchDataFromOutsideAngular();
  // Missing detectChanges call here
}

What problem will occur if detectChanges() is not called after updating data?

medium

A. The view will not update to show the new data.

B. Angular will throw a compilation error.

C. The app will crash at runtime.

D. The data will update but the component will reload.

Solution

1. Step 1: Understand change detection trigger

   Angular detects changes automatically only inside its own event flow.

2. Step 2: Effect of missing detectChanges()

   Since data is updated outside Angular's flow, the view won't update unless detectChanges() is called manually.

3. Final Answer:

   The view will not update to show the new data. -> Option A

4. Quick Check:

   Missing detectChanges() = view not updated [OK]

Hint: Without detectChanges(), view stays stale after external updates [OK]

Common Mistakes:

• Expecting Angular to auto-update view always
• Thinking missing detectChanges() causes errors
• Confusing data update with view update

5. You have a component that receives data updates from a WebSocket outside Angular's zone. Which approach correctly ensures the view updates when new data arrives?

hard

A. Reload the entire page when new data arrives.

B. Inject ChangeDetectorRef and call detectChanges() inside the WebSocket callback.

C. Use setTimeout without any change detection calls.

D. Call markForCheck() without injecting ChangeDetectorRef.

Solution

1. Step 1: Recognize updates outside Angular zone

   WebSocket callbacks run outside Angular's change detection zone, so Angular won't detect changes automatically.

2. Step 2: Use detectChanges() to update view

   Injecting ChangeDetectorRef and calling detectChanges() inside the callback forces Angular to update the view with new data.

3. Final Answer:

   Inject ChangeDetectorRef and call detectChanges() inside the WebSocket callback. -> Option B

4. Quick Check:

   Manual detectChanges() needed for external async updates [OK]

Hint: Use detectChanges() inside external async callbacks [OK]

Common Mistakes:

• Using markForCheck() without ChangeDetectorRef injection
• Relying on setTimeout alone to update view
• Reloading page instead of updating view