Skip to content

bug: missing route-level error boundaries in app routes #428

Description

@nanaf6203-bit

Summary

Several app routes lack an explicit error boundary, leaving failures to surface as the generic app/error.tsx or as an unhandled error.

Affected area

  • src/app/compare/page.tsx
  • src/app/governance/page.tsx
  • src/app/secondary-market/page.tsx
  • src/app/tax-report/page.tsx
  • src/app/mobile-properties/page.tsx
  • src/app/widget/investment-calculator/page.tsx
  • src/app/developers/tokenize/page.tsx

Steps to reproduce / impact

Trigger a render exception inside one of these pages and you get either a full white page or a generic boundary that doesn't preserve navigation. Users bounce.

Expected behaviour

Wrap each page with withRouteErrorBoundary (already exists in src/components/error/), or migrate to Next.js 14 error boundaries at the route segment level.

Acceptance criteria

  • All src/app/**/page.tsx files are covered.
  • Snapshot tests confirm boundary UI for caught errors.
  • Uncaught errors continue to bubble to app/error.tsx with breadcrumb context.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Stellar WaveIssues in the Stellar wave programbugSomething isn't working correctlypriority/p2P2 — medium priorityrefactorCode health / refactor (no behaviour change)

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions