Skip to content
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

fix(react): Set handled value in ErrorBoundary depending on fallback [v7] #11037

Merged
merged 2 commits into from Mar 12, 2024

Conversation

Lms24
Copy link
Member

@Lms24 Lms24 commented Mar 12, 2024

Backport of #10989 (forgot initially; got reminded via #10996)

#10989)

Previously, we made a change to always mark such errors as unhandled
(#8914). However, as pointed out and discussed in #10985, this isn't
always the best default value. I propose we set handled/unhandled
depending on the presence of the `fallback` component. If users specify
a fallback, I think it's safe to mark the error handled, given that
users show something else instead of the errored component.
@Lms24 Lms24 changed the base branch from develop to v7 March 12, 2024 09:51
@Lms24 Lms24 changed the title fix(react): Set handled value in ErrorBoundary depending on fallback fix(react): Set handled value in ErrorBoundary depending on fallback [v7] Mar 12, 2024
@Lms24 Lms24 mentioned this pull request Mar 12, 2024
@Lms24 Lms24 self-assigned this Mar 12, 2024
@Lms24 Lms24 requested review from lforst and AbhiPrasad March 12, 2024 09:53
@Lms24 Lms24 enabled auto-merge (squash) March 12, 2024 14:54
@Lms24 Lms24 merged commit 1c71e8e into v7 Mar 12, 2024
67 checks passed
@Lms24 Lms24 deleted the lms/fix-v7-react-errorboundary-handled-unhandled branch March 12, 2024 15:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants