Fixing Expression Has Changed After It Was Checked Error in Angular

[@MonsterlessonsAcademy]

WATCH NEXT: Angular Interview Questions and Answers - Dominate Your Next Interview - kzbin.info/www/bejne/a3LCin6ii7yAhtEsi=2DCn7yspEAAJ2H6l

[@jurybalikov7063]

As always, happy to see new videos. This will be a helpful video to anyone trying to fix this error, but I was expecting you to mention in the end of the video that all of these fixes are, well, fixes. And in reality, if you are running into this error, you are likely writing some anti-pattern code and should refactor it. Most likely, get rid of, as you called it, "nasty mutations" and side effects.

[@MonsterlessonsAcademy]

I agree, good architecture is important, but typically people just stumble across this error and don't understand at all what is the problem. Refactoring would be the next step.

[@deadlyecho]

You can also use ngzone run... but for this video, its better to refactor the code... I would say this video is just for learning purposes...

[@MonsterlessonsAcademy]

Yeap

[@sachin.tandon]

Great videos, I love them. Your explanations are so clear...even for a Cambridge / M.I.T. Engineer. For the above problem, there is a 4th way. I used to get it a lot and used the cdr and set Timeout solutions. Using signals / computed signals, viewChild, etc, overcomes the problem entirely.

[@MonsterlessonsAcademy]

Yeap. Everything will boil down to signals.

[@akuoko_konadu]

Thanks, for the video, I don't do manual change detection, mostly because I can forget to rerun CD, so I just stick with delay and setTimeout. I don't know but is there a way signals will fix this issue, cause I have heard that signals does not depend on angular change detection

[@MonsterlessonsAcademy]

They will. The future is that we don't need the whole traversing of components to make a component change detection and signals are going in that way.

[@mohamedyahyacheikhmaazouz1650]

Can you please make a video about how to get started with Next.js? I am a React.js developer, and I want to take my skills to the next level.

[@MonsterlessonsAcademy]

Unfortunately I don't have any good videos about Next.js for beginners.

[@code_with_rasta]

Thank you for this 😊

[@MonsterlessonsAcademy]

You're welcome 😊

[@MrKOHKyPEHT]

Also we can use "scheduler" instead "of"

[@MonsterlessonsAcademy]

Yeap

[@anutaNYC]

You can write afterviewinit without implementation AfterViewInit?!!

[@MonsterlessonsAcademy]

implementation will just be validated by typescript. you can skip ngOnInit in the same way

[@vandameh.a2235]

also you can do Promise.resolve().then() to solve this error, basically the same xd

[@MonsterlessonsAcademy]

Yeap

[@puneetarora1714]

I faced this error a few days back and boy it was a h**l to debug this and fix it in my unit tests

[@MonsterlessonsAcademy]

Yeap, I feel your pain.