feat(profile): preset date/time format picker + central formatter (frontend) #118
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!118
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "feat/pms-253-date-format-preference-frontend"
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?
Second half of PMS-253. Lands the consumer side of the per-user date/time format preference on the SPA: AuthContext now carries
date_format_string, the Profile page renders a "Date & time format" Select with eight presets right next to the timezone dropdown, and the centralcrate::utils::datetime::format_user_datetimehelper expands a moment-style token grammar (YYYY, MMM, DD, HH, mm, A, a.m., ...) against the user's stored format. A Custom... button sits below the dropdown, disabled with an inline "lands in a follow-up PR (PMS-254)" note, so the surface is in place for slice 2 to plug in.Initial migration covers the high-visibility sites called out in the issue: the notification bell (
format_local_datetimeincomponents/layout.rs), the audit log table, ticket SLA + activity timestamps, asset history, and the multi-tenant admin "created" column. Each fall back to the existing strftime when the user has no pref so existing users see no change.Helper ships with 9 unit tests covering every token group, ordinal day, AM/PM variants, 12h roll-over, literal punctuation pass-through, and a preset-table sanity check.
#PMS-253