feat(ux): consistent skeleton loaders across list and detail pages (PMS-353) #250
Loading…
Reference in a new issue
No description provided.
Delete branch "feat/pms-353-skeleton-loaders"
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?
What
Makes loading states consistent across the SPA (PMS-353). Adds two shared skeletons matching the existing
TableLoadingshimmer style and applies them everywhere a page previously rendered bare "Loading…" text.New components (
src/components/skeleton.rs):grid-cols-1 md:grid-cols-2 lg:grid-cols-3).Cardof shimmer rows for single-record detail pages.Converted
Table) -> shimmer rows.Already covered
Admin/Team render
TableLoadingon first paint viaDataTable, so the reviewer's blank-white-screen case is already handled - no change there. (AC2 verified in code.)Intentionally left (not page-level list/detail loaders)
Dropdown "Loading…"
SelectOptions, transient single-cell fallbacks for sub-resource rows,None-arm header-title "Loading…" fallbacks, and the calendar month / dispatch-board grid views (a Card-shaped skeleton does not fit a calendar grid).AC mapping
bg-gray-200 dark:bg-gray-700 rounded animate-pulse) as TableLoading, so the look matches.The optional lint from proposed approach #3 (flag ad-hoc
"Loading…"patterns) is not included - noted as a possible follow-up.Verification
wasm
cargo check,cargo clippy --target wasm32-unknown-unknown --lib -- -D warnings, andcargo fmt --all --checkall pass.#PMS-353