Misc captureOwnerStack cleanup after stable release
#7710
Merged
Conversation
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
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
eps1lon
force-pushed
the
sebbie/ownerstack-stable
branch
from
8b82f95 to
8102651
Compare
gaearon
approved these changes
Apr 2, 2025
1. Stop using `canary` for `captureOwnerStack` sandboxes 1. Remove remaining Canary badges from `captureOwnerStack` mentions
eps1lon
force-pushed
the
sebbie/ownerstack-stable
branch
from
8102651 to
71b68b7
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
Based on #7709
canaryforcaptureOwnerStacksandboxes: https://react-dev-git-fork-eps1lon-sebbie-ownerstac-d5d20b-fbopensource.vercel.app/reference/react/captureOwnerStack#enhance-a-custom-error-overlaycaptureOwnerStackmentions: https://react-dev-git-fork-eps1lon-sebbie-ownerstac-d5d20b-fbopensource.vercel.app/reference/react/Component#catching-rendering-errors-with-an-error-boundaryCloses #7659