fix(ChangeDetection): ngAfterViewChecked is called when ChangeDetecto…#9317
fix(ChangeDetection): ngAfterViewChecked is called when ChangeDetecto…#9317alfonso-presa wants to merge 1 commit into
Conversation
|
oh damn, I saw your previous PR was closed so spent a while making #9351 Still, I learned a lot doing it :D Will close mine. |
1fabcc0 to
3f763a2
Compare
…r is detached ngDoCheck, ngAfterViewChecked, ngAfterContentChecked and ngOnChanges should not be invoked when ChangeDetector is detached. fixes angular#7054
3f763a2 to
0a9233d
Compare
|
@timruffles I think it's my fault... because I referenced another issue in the commits fix statement. Sorry for that. I also realised thanks to your code that it was better to call the method |
|
I don't think this is correct. The change detector of a component refers to its template. E.g. setting the change detector to |
|
Just closed #7054. Closing this PR for now as well. |
|
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Please check if the PR fulfills these requirements
What kind of change does this PR introduce? (check one with "x")
What is the current behavior? (You can also link to an open issue here)
ngDoCheck, ngAfterViewChecked, ngAfterContentChecked and ngOnChanges are called when ChangeDetector is detached
What is the new behavior?
ngDoCheck, ngAfterViewChecked, ngAfterContentChecked and ngOnChanges are NOT called when ChangeDetector is detached
Does this PR introduce a breaking change? (check one with "x")
If this PR contains a breaking change, please describe the impact and migration path for existing applications: ...
Other information:
ngDoCheck, ngAfterViewChecked, ngAfterContentChecked and ngOnChanges should not be invoked when ChangeDetector is detached.
fixes #7054