Default change detection strategy in Angular - Step-by-Step Execution

Concept Flow - Default change detection strategy

Event triggers (click, async, etc.)

↓

Angular runs change detection

↓

Traverse component tree

↓

Check each component's bindings

↓

Update DOM if data changed

↓

Finish change detection cycle

Angular's default change detection runs on every event and checks all components for data changes, updating the DOM accordingly.

Execution Sample

Angular

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

@Component({
  selector: 'app-root',
  template: `<button (click)="increment()">Increment</button><p>{{count}}</p>`
})
export class AppComponent {
  count = 0;
  increment() { this.count++; }
}

A simple Angular component with a button that increments a count displayed on screen, triggering default change detection.

Execution Table

Step	Trigger	State Before	Action	State After	What Re-renders	DOM Change
1	Initial load	count=0	Render component	count=0	AppComponent	Display count=0
2	User clicks button	count=0	Call increment()	count=1	AppComponent	Update displayed count to 1
3	Change detection runs	count=1	Check bindings	count=1	AppComponent	No further changes
4	User clicks button again	count=1	Call increment()	count=2	AppComponent	Update displayed count to 2
5	Change detection runs	count=2	Check bindings	count=2	AppComponent	No further changes
6	No more events	count=2	No action	count=2	None	No DOM changes

💡 No more events trigger change detection, so Angular stops checking.

Variable Tracker

Variable	Start	After 1	After 2	Final
count	0	1	2	2

Key Moments - 2 Insights

Why does Angular check all components on every event?

Because the default strategy runs change detection for the entire component tree on every event, ensuring all data bindings are up to date as shown in steps 2 and 4 of the execution_table.

Does Angular update the DOM if the data hasn't changed?

No, Angular compares previous and current values during change detection and only updates the DOM if data changed, as seen in steps 3 and 5 where no DOM changes occur.

Visual Quiz - 3 Questions

Look at the execution table, what is the value of 'count' after step 2?

A 2

B 0

C 1

D Undefined

💡 Hint

Check the 'State After' column in row for step 2.

At which step does Angular update the DOM to show 'count' as 2?

A Step 4

B Step 5

C Step 3

D Step 6

💡 Hint

Look for the step where 'count' changes to 2 and DOM updates.

If no user clicks happen, what does Angular do according to the execution table?

A Runs change detection continuously

B Does nothing after initial load

C Updates DOM repeatedly

D Throws an error

💡 Hint

See step 6 where no events trigger change detection.

Concept Snapshot

Default change detection in Angular:
- Runs on every event (click, async, etc.)
- Checks all components in the tree
- Compares data bindings
- Updates DOM only if data changed
- Ensures UI stays in sync automatically

Full Transcript

Angular's default change detection strategy runs after every event like clicks or async operations. It traverses the entire component tree checking each component's data bindings. If it finds any changes, it updates the DOM to reflect the new data. For example, when a button click increments a count variable, Angular detects the change and updates the displayed count. If no changes occur, Angular skips DOM updates to optimize performance. This process repeats on every event, keeping the UI in sync with the data automatically.

Practice

1. What does the default change detection strategy in Angular do?

easy

A. Requires manual updates to the view

B. Automatically updates the view when data changes

C. Disables change detection entirely

D. Only updates the view on user interaction

Solution

1. Step 1: Understand default change detection behavior

   The default strategy automatically checks for data changes and updates the view accordingly.

2. Step 2: Compare with other options

   Other options require manual updates or disable detection, which is not the default behavior.

3. Final Answer:

   Automatically updates the view when data changes -> Option B

4. Quick Check:

   Default strategy = automatic update [OK]

Hint: Default means automatic view update on data change [OK]

Common Mistakes:

• Thinking manual update is default
• Confusing default with OnPush strategy
• Believing change detection is disabled by default

2. Which of the following is the correct way to set the default change detection strategy in an Angular component?

easy

A. @Component({ changeDetection: ChangeDetectionStrategy.OnPush })

B. @Component({ changeDetection: 'default' })

C. @Component({ changeDetection: ChangeDetectionStrategy.Default })

D. @Component({ changeDetection: 'Default' })

Solution

1. Step 1: Recall Angular syntax for change detection

   The changeDetection property expects a value from the ChangeDetectionStrategy enum, not a string.

2. Step 2: Identify correct enum usage

   ChangeDetectionStrategy.Default is the correct enum value for default strategy.

3. Final Answer:

   @Component({ changeDetection: ChangeDetectionStrategy.Default }) -> Option C

4. Quick Check:

   Use enum, not string, for changeDetection [OK]

Hint: Use ChangeDetectionStrategy.Default enum, not string [OK]

Common Mistakes:

• Using strings instead of enum values
• Confusing 'default' with 'Default' string
• Mixing OnPush with default strategy

3. Consider this Angular component using the default change detection strategy:

@Component({
  selector: 'app-counter',
  template: `Count: {{count}}`
})
export class CounterComponent {
  count = 0;
  increment() {
    this.count++;
  }
}

What will happen when the button is clicked?

medium

A. An error will occur because change detection is disabled

B. The displayed count will not change until manually refreshed

C. The count will increase but the view will not update

D. The displayed count will increase by 1 automatically

Solution

1. Step 1: Understand default change detection behavior on event

   Default strategy runs change detection automatically after events like button clicks.

2. Step 2: Predict view update

   When increment() updates count, the view updates automatically to show the new count.

3. Final Answer:

   The displayed count will increase by 1 automatically -> Option D

4. Quick Check:

   Default strategy updates view on event [OK]

Hint: Default strategy updates view after events automatically [OK]

Common Mistakes:

• Thinking manual refresh is needed
• Assuming change detection is off
• Believing count changes but view stays same

4. You have this Angular component:

@Component({
  selector: 'app-sample',
  template: `{{value}}`
})
export class SampleComponent {
  value = 10;

  updateValue() {
    this.value = 20;
  }
}

After calling updateValue(), the view does not update. What is the most likely cause?

medium

A. The updateValue method is not called inside Angular zone

B. The default change detection strategy is disabled by mistake

C. The component uses OnPush strategy but input did not change

D. The value property is private and not accessible in template

Solution

1. Step 1: Check default strategy behavior

   Default strategy updates view automatically unless changes happen outside Angular zone.

2. Step 2: Identify cause of no update

   If updateValue() runs outside Angular zone, change detection won't trigger, so view stays old.

3. Final Answer:

   The updateValue method is not called inside Angular zone -> Option A

4. Quick Check:

   Outside Angular zone blocks default detection [OK]

Hint: Changes outside Angular zone don't trigger default detection [OK]

Common Mistakes:

• Assuming default strategy is disabled
• Confusing OnPush input change with default strategy
• Thinking private properties cause no update

5. In a large Angular app, you want to optimize performance by reducing unnecessary view updates. You decide to keep the default change detection strategy but want to limit checks on a specific component. Which approach fits best?

hard

A. Use ChangeDetectorRef.detach() to stop change detection on that component manually

B. Set changeDetection: ChangeDetectionStrategy.Default on that component

C. Use markForCheck() to force detection every time

D. Replace default strategy with OnPush on all components

Solution

1. Step 1: Understand default strategy limits

   Default strategy runs change detection frequently, which can be costly in large apps.

2. Step 2: Identify how to limit detection on one component

   Using ChangeDetectorRef.detach() stops change detection on that component until manually reattached.

3. Step 3: Evaluate other options

   Setting default again does nothing new; markForCheck forces detection; OnPush changes strategy globally, not selectively.

4. Final Answer:

   Use ChangeDetectorRef.detach() to stop change detection on that component manually -> Option A

5. Quick Check:

   Detach stops detection selectively [OK]

Hint: Detach change detector to pause updates on specific component [OK]

Common Mistakes:

• Thinking setting default again limits detection
• Confusing markForCheck with stopping detection
• Assuming OnPush is selective per component