Feat/error boundary component#470
Merged
Chucks1093 merged 2 commits intoJun 26, 2026
Merged
Conversation
- Rewrite .env.example with a one-line description for every variable and remove duplicate entries; group into required vs optional - Add an 'Environment variables' section to CONTRIBUTING.md covering required vs optional vars and where to source testnet RPC URLs
Closes accesslayerorg#424 Add a React error boundary scoped to creator detail pages so a render error shows a fallback UI instead of crashing the whole app to a blank screen. Follows the existing SectionErrorBoundary class pattern. - Fallback shows a short message and a "Back to creators" link (/creators) - Logs the error to console only in development (import.meta.env.DEV) - Add tests covering normal render, fallback on error, and the list link
|
@T-kesh Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits. You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀 |
3 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.
Summary
Closes #424. A render error on a creator page currently takes down the whole app to a blank screen. This adds CreatorPageErrorBoundary, a React error boundary scoped to creator detail pages that catches render errors and shows a fallback UI while keeping the rest of the app functional.
Changes
⚠️ pnpm build fails on a pre-existing vite:html-inline-proxy error in index.html — reproduced on the base branch with these changes stashed, so it's unrelated to this PR.
src/components/common/CreatorPageErrorBoundary.tsx — class-based error boundary following the existing SectionErrorBoundary pattern:
getDerivedStateFromError renders a fallback instead of letting the error bubble to the root
componentDidCatch logs the error to console only in development (import.meta.env.DEV)
Fallback shows a short message and a Back to creators link to /creators, using the app's Button asChild + Link (react-router v7) conventions
src/components/common/tests/CreatorPageErrorBoundary.test.tsx — tests for normal render, fallback on a thrown render error, and the link back to the creator list
Acceptance criteria
Render error on a creator page shows fallback UI instead of blank screen
Rest of the app (navigation, other routes) remains functional — boundary is scoped, not at root
Fallback includes a link back to the creator list
Verification
pnpm vitest run — new suite passes (3/3)
pnpm lint — clean
tsc -b type-check passes