Optimize and debug change detection like a pro
summary
Explains exactly what change detection does under the hood: components map to views with per-binding old values, Angular runs bindings then a dev-mode recheck that throws ExpressionChangedAfterItHasBeenChecked, and that explains surprising millisecond mismatches. Shows live debugging by breaking inside checkAndUpdateView, demonstrates setInterval + running outside NgZone to avoid the error, and compares behavior changed by Ivy so attendees can pick the right optimization and fix failures reliably.
AI-written summary · about
chapters (21)
- 0:00Intro
- 0:25About Max
- 1:53What is change detection
- 3:55Maxs background
- 4:45Angular in Depth
- 5:08Widget
- 6:03Error
- 7:39Template
- 9:47How they are used
- 12:20What happened in our case
- 13:15The solution
- 14:58What is zonegs
- 17:41Summary
- 18:20View bindings
- 19:03Debug change detection
- 20:11Unidirectional data flow
- 24:06Order of operations
- 24:46Parent component change detection
- 26:38Recommended articles
- 28:20Tshirt
- 28:51Conclusion
related talks
19mThe Magic and Mystery of Angular Change Detection
01h 02mChange Detection, Zone.js and Other Monsters
44mAngular 2 Change Detection Explained
12mNG-BE 2019 - Platinum Sponsor - Ordina
33mAngular 2 change detection explained
46mAngular 2 Change Detection Explained
17mNavigating Angular's Evolution for Peak Performance!
41mState of change detection in Angular and how far are we from Zoneless applications ?