peter
d794524adf
Add theme-scoped --danger/--warn/--success (+ -fg) tokens wired into the v4 @theme inline, replacing ~110 raw red/amber/emerald/green palette refs across 34 files. Fixes light-theme contrast failures (fixed Tailwind shades fell to ~1.7-3:1 on white). Status colors are scheme-independent — recognised by hue, shifting only by theme to hold contrast (bright on dark bg, darkened on light). Solid fills use the paired -fg text; @source inline guarantees the full -fg set exists. IMDb rating gold kept as a deliberate decorative non-status exception.
68 lines
2.7 KiB
TypeScript
68 lines
2.7 KiB
TypeScript
import type { ReactNode } from "react";
|
|
import { useTranslation } from "react-i18next";
|
|
import { AlertTriangle, Loader2 } from "lucide-react";
|
|
|
|
// Centered loading state: a spinning accent ring + an optional label. The single shared loading
|
|
// visual for a page/section's first load, so all of them read the same (and can be swapped for
|
|
// skeletons later in one place). `role=status`/`aria-live` announces it to screen readers.
|
|
export function LoadingState({ label, className = "" }: { label?: ReactNode; className?: string }) {
|
|
const { t } = useTranslation();
|
|
return (
|
|
<div
|
|
className={`flex flex-col items-center gap-3 py-10 text-sm text-muted ${className}`}
|
|
role="status"
|
|
aria-live="polite"
|
|
>
|
|
<Loader2 className="w-6 h-6 animate-spin text-accent" aria-hidden />
|
|
<span>{label ?? t("common.loading")}</span>
|
|
</div>
|
|
);
|
|
}
|
|
|
|
// Centered inline status line for a page/section's loading and error(+retry) states, in the house
|
|
// style (mirrors Playlists' error block). Text-only by design — R3's goal is to stop pages
|
|
// rendering an error or a still-loading fetch AS an "empty" state, not to add skeletons. The
|
|
// `role=status`/`aria-live` also gives screen readers the state change (the app had zero live
|
|
// regions before).
|
|
export function StateMessage({
|
|
children,
|
|
onRetry,
|
|
tone = "muted",
|
|
className = "",
|
|
}: {
|
|
children: ReactNode;
|
|
onRetry?: () => void;
|
|
tone?: "muted" | "error";
|
|
className?: string;
|
|
}) {
|
|
const { t } = useTranslation();
|
|
return (
|
|
<div
|
|
className={`flex flex-col items-center gap-3 py-10 text-sm text-muted ${className}`}
|
|
// An error is announced promptly (assertive); a plain loading line is polite.
|
|
role={tone === "error" ? "alert" : "status"}
|
|
aria-live={tone === "error" ? "assertive" : "polite"}
|
|
>
|
|
<span className="inline-flex items-center gap-2 text-center">
|
|
{tone === "error" && <AlertTriangle className="w-4 h-4 shrink-0 text-danger" />}
|
|
{children}
|
|
</span>
|
|
{onRetry && (
|
|
<button
|
|
type="button"
|
|
onClick={onRetry}
|
|
className="px-3 py-1.5 rounded-lg border border-border text-xs text-muted hover:text-fg hover:border-accent transition"
|
|
>
|
|
{t("common.retry")}
|
|
</button>
|
|
)}
|
|
</div>
|
|
);
|
|
}
|
|
|
|
// The honest-state convention every page now follows: check `isError && <no data>` BEFORE the empty
|
|
// branch, so a failed fetch renders this message (with Retry) instead of the page's "empty" text
|
|
// — the R3 bug where a backend restart read as "No channels". The `&& <no data>` guard matters: a
|
|
// transient refetch error while data is already on screen keeps the data rather than blanking it to
|
|
// an error. `StateMessage` is the shared building block pages wire into their loading/empty ternary.
|