feat(routes): wrap Outlet in ErrorBoundary with recoverable fallback (MAPPS-318) #363

Merged

YousifShkara merged 1 commit from feat/MAPPS-318-route-error-boundary into main

2026-06-26 06:37:38 +02:00

YousifShkara commented

2026-06-26 06:06:30 +02:00

Owner

A single route returning Err(...) (via ? or bail!) previously poisoned the AuthGuard's Outlet, leaving the user on a URL that did not render anything actionable. Wrap the Outlet in dioxus::ErrorBoundary with a centered RouteErrorFallback card that offers "Go to dashboard" (clears the boundary + navigates) and "Reload page" (window.location.reload). Debug builds also print the captured error in a code block so QA can paste it into bug reports.

The boundary does NOT catch wasm panics. dioxus-core 0.7 documents that CapturedPanic is unreachable on wasm because the runtime cannot unwind, so panic!() still aborts. The fix covers every error that flows through the Element = Result<VNode, RenderError> channel; panic recovery is parked until upstream wasm supports catching unwinds. Inline comment + ticket update flag the limitation explicitly.

#MAPPS-318

A single route returning `Err(...)` (via `?` or `bail!`) previously poisoned the AuthGuard's Outlet, leaving the user on a URL that did not render anything actionable. Wrap the Outlet in `dioxus::ErrorBoundary` with a centered `RouteErrorFallback` card that offers "Go to dashboard" (clears the boundary + navigates) and "Reload page" (window.location.reload). Debug builds also print the captured error in a code block so QA can paste it into bug reports. The boundary does NOT catch wasm panics. dioxus-core 0.7 documents that `CapturedPanic` is unreachable on wasm because the runtime cannot unwind, so `panic!()` still aborts. The fix covers every error that flows through the `Element = Result<VNode, RenderError>` channel; panic recovery is parked until upstream wasm supports catching unwinds. Inline comment + ticket update flag the limitation explicitly. #MAPPS-318

YousifShkara self-assigned this

2026-06-26 06:06:30 +02:00

YousifShkara added 1 commit

2026-06-26 06:06:30 +02:00

feat(routes): wrap Outlet in ErrorBoundary with recoverable fallback (MAPPS-318)

Check / fmt + clippy + tests (pull_request) Successful in 12m3s

Details

Create release / Create release from merged PR (pull_request) Has been skipped

Details

c08209cfa8

A single route returning `Err(...)` (via `?` or `bail!`) previously poisoned the AuthGuard's Outlet, leaving the user on a URL that did not render anything actionable. Wrap the Outlet in `dioxus::ErrorBoundary` with a centered `RouteErrorFallback` card that offers "Go to dashboard" (clears the boundary + navigates) and "Reload page" (window.location.reload). Debug builds also print the captured error in a code block so QA can paste it into bug reports.

The boundary does NOT catch wasm panics. dioxus-core 0.7 documents that `CapturedPanic` is unreachable on wasm because the runtime cannot unwind, so `panic!()` still aborts. The fix covers every error that flows through the `Element = Result<VNode, RenderError>` channel; panic recovery is parked until upstream wasm supports catching unwinds. Inline comment + ticket update flag the limitation explicitly.

#MAPPS-318

YousifShkara merged commit f021b14220 into main

2026-06-26 06:37:38 +02:00

YousifShkara deleted branch feat/MAPPS-318-route-error-boundary

2026-06-26 06:37:38 +02:00

YousifShkara referenced this pull request from a commit

2026-06-26 06:37:40 +02:00

Merge pull request 'feat(routes): wrap Outlet in ErrorBoundary with recoverable fallback (MAPPS-318)' (#363) from feat/MAPPS-318-route-error-boundary into main