feat(frontend): route-segment error.tsx for claims, policies, and admin - #269
Merged
Conversation
|
@AustineSamuel 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! 🚀 |
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.
Closes #238
Adds and wires Next.js App Router segment error boundaries so a render failure in one area does not tear down the whole shell (nav, wallet, etc.).
Segments
/policies — new layout + page hosting PolicyDashboard; error.tsx for this subtree.
/claims — existing error.tsx updated to pass a segment key for logging.
/admin — new placeholder layout + page + error.tsx (robots already disallow /admin).
Recovery UX
Shared RouteError: contextual title, user-safe message (no stack in prod), Try again calling reset(), Go to dashboard ( /dashboard → /redirect to /policies).
Observability
logRouteSegmentError → Plausible route_segment_error with segment, error_name, optional digest only (no error.message, no stack to analytics).