Skip to content

fix(core): afterRender hooks registered outside change detection can …#55623

Closed
atscott wants to merge 1 commit intoangular:mainfrom
atscott:renderhookloop
Closed

fix(core): afterRender hooks registered outside change detection can …#55623
atscott wants to merge 1 commit intoangular:mainfrom
atscott:renderhookloop

Conversation

@atscott
Copy link
Contributor

@atscott atscott commented May 1, 2024

…mark views dirty

This commit fixes an error in the looping logic of ApplicationRef.tick when the tick skips straight to render hooks. In this case, if a render hook makes a state update that requires a view refresh, we would never actually refresh the view and just loop until we hit the loop limit.

@atscott atscott added the target: rc This PR is targeted for the next release-candidate label May 1, 2024
@atscott atscott requested a review from alxhub May 1, 2024 22:29
@atscott atscott added the action: merge The PR is ready for merge by the caretaker label May 1, 2024
…mark views dirty

This commit fixes an error in the looping logic of `ApplicationRef.tick`
when the tick skips straight to render hooks. In this case, if a render
hook makes a state update that requires a view refresh, we would never
actually refresh the view and just loop until we hit the loop limit.
@atscott atscott added the merge: caretaker note Alert the caretaker performing the merge to check the PR for an out of normal action needed or note label May 2, 2024
@atscott
Copy link
Contributor Author

atscott commented May 2, 2024

caretaker note: g3 failures are unrelated

@AndrewKushnir
Copy link
Contributor

This PR was merged into the repository by commit 7c1b4a4.

AndrewKushnir pushed a commit that referenced this pull request May 2, 2024
…mark views dirty (#55623)

This commit fixes an error in the looping logic of `ApplicationRef.tick`
when the tick skips straight to render hooks. In this case, if a render
hook makes a state update that requires a view refresh, we would never
actually refresh the view and just loop until we hit the loop limit.

PR Close #55623
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Jun 2, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

action: merge The PR is ready for merge by the caretaker merge: caretaker note Alert the caretaker performing the merge to check the PR for an out of normal action needed or note target: rc This PR is targeted for the next release-candidate

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants