paint-brush
Everything you need to know about the `ExpressionChangedAfterItHasBeenCheckedError` errorby@maxim.koretskyi
81,458 reads
81,458 reads

Everything you need to know about the `ExpressionChangedAfterItHasBeenCheckedError` error

by Maxim Koretskyi9mJuly 1st, 2017
Read on Terminal Reader
Read this story w/o Javascript
tldt arrow
EN

Too Long; Didn't Read

It seems that recently almost every day there’s a question on stackoverflow regarding the ExpressionChangedAfterItHasBeenCheckedError error thrown by Angular. Usually these questions come up because Angular developers do not understand how change detection works and why the check that produces this error is required. Many developers even view it as a bug. But it’s certainly not. This is a a cautionary mechanism put in place to prevent inconsistencies between model data and UI so that erroneous or old data are not shown to a user on the page.

Company Mentioned

Mention Thumbnail

Coin Mentioned

Mention Thumbnail
featured image - Everything you need to know about the `ExpressionChangedAfterItHasBeenCheckedError` error
Maxim Koretskyi HackerNoon profile picture
Maxim Koretskyi

Maxim Koretskyi

@maxim.koretskyi

L O A D I N G
. . . comments & more!

About Author

TOPICS

Languages

THIS ARTICLE WAS FEATURED IN...

Permanent on Arweave
Read on Terminal Reader
Read this story in a terminal
 Terminal
Read this story w/o Javascript
Read this story w/o Javascript
 Lite