feat(react): Rename ErrorBoundary onError to onCatch (BREAKING CHANGE)
#1784
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 GitHub.
|
Co-authored-by: manudeli <[email protected]>
Co-authored-by: manudeli <[email protected]>
People can be co-author:
|
Co-authored-by: manudeli <[email protected]>
manudeli
reviewed
Oct 15, 2025
| .ErrorBoundary({ | ||
| fallback: ({ error }) => <>{error.message}</>, | ||
| onError: logger.log, | ||
| onCatch: logger.log, |
Member
There was a problem hiding this comment.
@copilot This is a migration guide from v1 to v2. Please do not do this.
Not only this MDX, but other migration docs should also be kept
Contributor
Author
There was a problem hiding this comment.
Reverted the changes to both English and Korean v1-to-v2 migration docs. These docs should remain unchanged as they document the historical migration from v1 to v2. (commit e5cc944)
Copilot
AI
changed the title
[WIP] Rename onError prop to onCatch with breaking change
feat(react): Rename ErrorBoundary Oct 15, 2025
onError to onCatch (BREAKING CHANGE)
Copilot finished work on behalf of
manudeli
October 15, 2025 05:42
|
Size Change: -12 B (-0.01%) Total Size: 80.2 kB
ℹ️ View Unchanged
|
Co-authored-by: manudeli <[email protected]>
Copilot finished work on behalf of
manudeli
October 15, 2025 05:48
Member
|
@copilot |
Co-authored-by: manudeli <[email protected]>
Contributor
Author
Created migrate-to-v4 migration guides for both English and Korean following the same format as other migration guides. The guides document the |
Copilot finished work on behalf of
manudeli
October 15, 2025 05:53
…h renaming in English and Korean documentation
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.
onErrorprop toonCatchin ErrorBoundary types (ErrorBoundaryProps)onCatchinstead ofonErroronCatchinstead ofonErrorUpdate migration documentation (migrate-to-v2.mdx for both en and ko)Reverted - v1-to-v2 migration docs should remain unchangedonErrortoonCatch(both English and Korean)onCatchAll changes have been successfully completed! The ErrorBoundary component now uses
onCatchinstead ofonErroras the prop name, which better aligns with the naming convention (matchingshouldCatchandcomponentDidCatch).Migration Guide
A comprehensive migrate-to-v4 guide has been added to help users transition from
onErrortoonCatch. The guide includes:ErrorBoundary.withpatternNote: The v1-to-v2 migration documentation has been kept unchanged as it documents historical migration from v1 to v2, not current v4 changes.
Fixes #1783
Original prompt
Fixes #1783
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.