liveBook · Manning

Change detection

Change detection is the process of identifying relevant differences between successive states and determining the updates required in response.

How 2 Manning books explain it

Modern Angular

Angular change detection is the framework process that checks data bindings for changes and updates the rendered view accordingly.

How it is used
Propagates component-state changes through template bindings to render updated Angular views.
How deep it goes
Explains binding checks, lifecycle timing, Zone.js costs, signal behavior, and testing implications; defers the full mechanism beyond this overview.
Examples
Uses a click-updated `name` binding, a repeatedly called `fullName()` template function, and TestBed stub-component tests.
What you can do after
Diagnose/debug with it by identifying unnecessary template-function calls and triggering lifecycle-bound signal updates in tests.

Read how Modern Angular explains change detection →

Pro Angular 16

Change detection is Angular's process for detecting changes in application state and updating affected views.

How it is used
Reflects user interactions and data updates in HTML while framing the trade-off between conventional checks and signals.
How deep it goes
Explains triggering, template-expression evaluation, selective DOM updates, and redundant work; does not detail binding types.
Examples
Uses console-logged getters, an expensive count calculation, a mouseover-highlighted product row, and an Angular Material table.
What you can do after
Diagnose/debug with browser-console logs when an interaction reevaluates unaffected getters and causes slow updates.

Read how Pro Angular 16 explains change detection →

Related concepts

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.