docs: document hydration completion check for e2e tests#68082
Closed
splincode wants to merge 1 commit intoangular:mainfrom
Closed
docs: document hydration completion check for e2e tests#68082splincode wants to merge 1 commit intoangular:mainfrom
splincode wants to merge 1 commit intoangular:mainfrom
Conversation
Add guidance to the hydration guide so E2E tests can reliably wait for client-side hydration to complete by observing the removal of Angular's temporary ngh attributes on component hosts.
Contributor
|
I don't think we'd want to recommend this. The |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the new behavior?
Add guidance to the hydration guide so E2E tests can reliably wait for client-side hydration to complete by observing the removal of Angular's temporary ngh attributes on component hosts.
Does this PR introduce a breaking change?