feat(frontend): implement react error boundaries (#188) - #196
Merged
Sendi0011 merged 4 commits intoJul 25, 2026
Conversation
Sendi0011
self-requested a review
July 24, 2026 07:08
Sendi0011
reviewed
Jul 24, 2026
Sendi0011
left a comment
Sendi0011
left a comment
Contributor
There was a problem hiding this comment.
This looks great @JenyferMontano kindly fix the failing CI then i will merge afterward
JenyferMontano
force-pushed
the
feat/react-error-boundaries
branch
from
July 25, 2026 20:54
9feaace to
1aaf4a9
Compare
Contributor
Author
|
Hi @Sendi0011 I've resolved the merge conflicts and updated the Prettier formatting. The PR is clean and ready, but the GitHub Actions workflows are currently awaiting maintainer approval to run. Could you please approve them so the CI checks can complete? Thanks! |
Sendi0011
self-requested a review
July 25, 2026 21:09
Sendi0011
approved these changes
Jul 25, 2026
Sendi0011
left a comment
Sendi0011
left a comment
Contributor
There was a problem hiding this comment.
Looks Great @JenyferMontano , thanks -approving
LGTM👍
7 tasks
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
2 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.
Description
This PR introduces React error boundaries across the entire dashboard to prevent full-page crashes when a component throws an unexpected error. It includes the
ErrorBoundarywrapper component, page-level wrapping, granular section boundaries (e.g., in Group Details), and a rate-limited error reporting utility that logs client errors to/api/errors.Closes #188
Type of Change
How Has This Been Tested?
I ran the local dev server and simulated UI crashes by throwing errors inside the components to ensure the fallback UI renders correctly. I also verified the backend API rate limiting and logging, and added unit tests for the error boundary logic.
cargo testpasses (smart contracts)pnpm buildsucceeds (frontend)pnpm lintpasses (frontend)app/explore/page.tsxto verify the full-page fallback UI.components/group/group-details.tsxto verify the compact section fallback UI.cron_job_logstable via the/api/errorsendpoint.Checklist
Screenshots (if applicable)