-
Notifications
You must be signed in to change notification settings - Fork 27k
refactor(core): Consolidates shouldTrigger* methods down to one #58833
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
48cb799 to
1be4c04
Compare
1be4c04 to
4e1607d
Compare
This adds TDeferDetailsFlags to indicate the presence of hydration triggers, and any future flags we add to defer.
4e1607d to
79c82fd
Compare
79c82fd to
3a4953f
Compare
AndrewKushnir
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, just a few minor comments (in docs and tests).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we need to wait for 1 second here? We can probably replace this with:
| await timeout(1000); // wait for defer blocks to resolve | |
| await allPendingDynamicImports(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've actually gone through and updated every location with this. Extra bonus: tests run in 1/3rd of the time now.
This cleans up the triggering code base and consolidates it down to one function that outlines the logic. This also resolves the `hydrate when` behavior issue. fixes: angular#58709
d6af9a4 to
2c52299
Compare
|
This PR was merged into the repository by commit 30891d8. The changes were merged into the following branches: main, 19.0.x |
This adds TDeferDetailsFlags to indicate the presence of hydration triggers, and any future flags we add to defer. PR Close #58833
|
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. |
This removes potential confusion by relying on one shouldTriggerDeferBlock method everywhere.
PR Type
What kind of change does this PR introduce?
Does this PR introduce a breaking change?