-
-
Notifications
You must be signed in to change notification settings - Fork 8.5k
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(core): ensure core error boundary is able to render theme layout #9852
Merged
Conversation
This file contains 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
✅ [V2]
To edit notification comments on pull requests, go to your Netlify site configuration. |
slorber
added
pr: bug fix
This PR fixes a bug in a past release.
to backport
This PR is planned to be backported to a stable version of Docusaurus
labels
Feb 15, 2024
⚡️ Lighthouse report for the deploy preview of this PR
|
Size Change: +162 B (0%) Total Size: 992 kB
ℹ️ View Unchanged
|
This was referenced May 19, 2024
This was referenced May 26, 2024
This was referenced May 27, 2024
This was referenced May 28, 2024
This was referenced Aug 21, 2024
This was referenced Aug 27, 2024
This was referenced Sep 4, 2024
This was referenced Sep 8, 2024
This was referenced Sep 11, 2024
This was referenced Sep 28, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
CLA Signed
Signed Facebook CLA
pr: bug fix
This PR fixes a bug in a past release.
to backport
This PR is planned to be backported to a stable version of Docusaurus
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.
Motivation
There are cases where the core React error boundary will catch a React rendering error, and display a fallback UI, trying to eventually display that error in the current theme layout.
But due to a missing
routeContext
, the classic theme layout will always error, trigger the re-rendering of the error without the theme layout, and produce unexpected error messages unrelated to the user's mistake.Notably, the classic theme layout uses
useRouteContext()
to retrieve the current plugin name and add it to<html>
classes, for CSS targeting purposes. But the core error boundary will try to render the theme layout without and route context provider, so it crashes:We should prevent that from happening and make it possible to render caught errors inside the theme layout whenever possible.
For that reason I'm adding a kind-of artificial route context for rendering caught errors. It's not super elegant but it solves the problem.
Before:
console:
After:
console:
Test Plan
none, local test 😅
Test links
https://deploy-preview-9852--docusaurus-2.netlify.app/