Repository navigation
Docs Document cleanup when replacing renderIntoDocument - #8719
Open
Jubayeromi wants to merge 3 commits into
Open
Jubayeromi wants to merge 3 commits into
Jubayeromi wants to merge 3 commits into
Conversation
Size changesDetails📦 Next.js Bundle Analysis for react-devThis analysis was generated by the Next.js Bundle Analysis action. 🤖 This PR introduced no changes to the JavaScript bundle! 🙌 |
This branch was successfully deployed
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
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.
##28
Clarify how to clean up rendered components when migrating from renderIntoDocument() to React Testing Library’s render(). Document the returned unmount function, automatic test cleanup, and handling portals or separate roots.
Related issue: react/react#10330
Because the issue is in the react/react repository, reference it by its full repository and issue number rather than using Fixes #10330 in a react.dev PR