Benjamin_Boenisch/breakpilot-compliance
1
0
Fork 0
Code Issues 24 Pull Requests Actions Packages Projects Releases Wiki Activity

Add error boundaries to all SDK route pages #25

New Issue
Open
opened 2026-04-20 09:37:48 +00:00 by sharang · 0 comments
sharang commented 2026-04-20 09:37:48 +00:00
Owner
Copy Link
Copy Source

Problem

SDK pages in admin-compliance/app/(sdk)/ do not have error boundaries. If any component throws an uncaught error (network failure, null data, unexpected API shape), the entire page goes blank with no user-facing message. React's default behavior in production is to unmount the whole tree.

Required Actions

  1. Create admin-compliance/components/sdk/ErrorBoundary.tsx — class component with componentDidCatch that renders a fallback UI
  2. Wrap every SDK route layout in the error boundary:
    • app/(sdk)/layout.tsx — wraps all SDK pages
    • Individual pages with complex data fetching can add inner boundaries
  3. Fallback UI should show: service name, generic error message, retry button
  4. Log caught errors to a structured logger (console.error with context in dev, error tracking service in prod)

Acceptance Criteria

  • Simulated API failure shows a friendly error state, not a blank page
  • Error boundary catches thrown errors in child components
  • Fallback includes a user-actionable recovery option (retry / go to dashboard)
## Problem SDK pages in `admin-compliance/app/(sdk)/` do not have error boundaries. If any component throws an uncaught error (network failure, null data, unexpected API shape), the entire page goes blank with no user-facing message. React's default behavior in production is to unmount the whole tree. ## Required Actions 1. Create `admin-compliance/components/sdk/ErrorBoundary.tsx` — class component with `componentDidCatch` that renders a fallback UI 2. Wrap every SDK route layout in the error boundary: - `app/(sdk)/layout.tsx` — wraps all SDK pages - Individual pages with complex data fetching can add inner boundaries 3. Fallback UI should show: service name, generic error message, retry button 4. Log caught errors to a structured logger (console.error with context in dev, error tracking service in prod) ## Acceptance Criteria - Simulated API failure shows a friendly error state, not a blank page - Error boundary catches thrown errors in child components - Fallback includes a user-actionable recovery option (retry / go to dashboard)
sharang added this to the M5: Frontend Hardening milestone 2026-04-20 09:37:48 +00:00
sharang added the reliabilityfrontendseverity: medium labels 2026-04-20 09:37:48 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
config
Env vars, secrets management, startup validation
 data-integrity
Transactions, indexes, pagination
 frontend
Next.js, client-side concerns
 observability
Logging, audit trails, health checks
 reliability
Error handling, retries, circuit breakers
 security
Auth, secrets, injection, tenant isolation
 severity: critical
System-level risk, data breach or full outage
 severity: high
Significant risk, must fix before go-live
 severity: medium
Important but not blocking go-live
 testing
Test coverage, integration tests
No Label frontend reliability severity: medium
Milestone
No items
No Milestone M5: Frontend Hardening
Projects
Clear projects
No project
Assignees
Clear assignees
sharang (Sharang Parnerkar) Benjamin_Boenisch
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Benjamin_Boenisch/breakpilot-compliance#25
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?