feat(dashboards): management page for saved dashboards (PMS-453 phase 1 client) #322
No reviewers
Labels
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
psa-systems/mokosh-apps!322
Loading…
Reference in a new issue
No description provided.
Delete branch "feat/PMS-453-saved-dashboards-client"
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?
Adds
/dashboardsto the SPA: a tenant-scoped list of the caller's own saved dashboards (default-first), a "New dashboard" modal that creates a row and optionally pins it as the post-login default, a "Pin default" row action that swaps the pinned row, and a "Delete" row action. Round-trips through the API surface added on the server infeat/PMS-453-saved-dashboardsand treats thelayoutJSONB as opaque; the widget surface that consumes the blob is a follow-up.This is purely the management surface. The existing
/dashboard(singular, hardcoded) page is untouched; once the widget surface lands the auth shell will redirect a logged-in user to their pinned default dashboard's/dashboards/<id>route instead.Wires
patch_authed/patch_with_authinto the fetch hook so the new module's partial-update endpoint has a typed client without inviting other call sites to overwrite whole rows.#PMS-453