Skip to content

xbignell/angular-expression-has-changed-error

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

31 Commits
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Expression has changed after it was checked

Analysis of the headache error "NG0100: Expression has changed after it was checked"

Trying to show why this error is happening with the less code possible.

Why "Expression has changed after it was checked" is useful?

What would happen if the view generation process could itself modify the rendered data? This could be very problematic, to start we could even create an infinite loop!

Read more 📓

Edit on StackBlitz ⚡️

Releases

No releases published

Packages

No packages published