refactor: share page loading and error states #430

New issue

Open

opened 2026-07-21 14:12:31 +02:00 by dries · 0 comments

dries commented

2026-07-21 14:12:31 +02:00

Owner

What to build

Introduce narrow shared components for the identical dashboard list-loading state and ordinary page-level error banner. Use them only where existing markup matches; retain specialized skeletons, error boundaries, composer errors, and domain-specific empty states.

Acceptance criteria

Identical spinner-and-label states use one accessible loading component.
Ordinary page errors use one alert component with optional retry action.
Shared states provide consistent status or alert semantics.
Specialized loading and error experiences remain separate.
Frontend tests cover labels, accessibility semantics, and optional actions.

Blocked by

None - can start immediately.

## What to build Introduce narrow shared components for the identical dashboard list-loading state and ordinary page-level error banner. Use them only where existing markup matches; retain specialized skeletons, error boundaries, composer errors, and domain-specific empty states. ## Acceptance criteria - [ ] Identical spinner-and-label states use one accessible loading component. - [ ] Ordinary page errors use one alert component with optional retry action. - [ ] Shared states provide consistent status or alert semantics. - [ ] Specialized loading and error experiences remain separate. - [ ] Frontend tests cover labels, accessibility semantics, and optional actions. ## Blocked by None - can start immediately.