feat: Implement Error Boundaries to prevent full-app crashes#83
Open
jpdevhub wants to merge 2 commits into
Open
feat: Implement Error Boundaries to prevent full-app crashes#83jpdevhub wants to merge 2 commits into
jpdevhub wants to merge 2 commits into
Conversation
|
@jpdevhub is attempting to deploy a commit to the razen04's projects Team on Vercel. A member of the Team first needs to authorize it. |
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
1 participant
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.
This PR adds React Error Boundaries across the app using the standard react-error-boundary library. Instead of a single glitch causing the entire app to show a "white screen of death," errors are now contained safely.
Why it matters: This makes the app feel much more like a stable, native application and prevents users from losing their session data just because one small piece of the UI failed.
issue #77