Add a user preference for the displayed date format#2110
Open
frankrousseau wants to merge 1 commit into
Open
Conversation
Add a per-user preference to render dates as DD/MM/YYYY or MM/DD/YYYY instead of the fixed ISO format. The preference is stored in the person record generic data field, so it follows the user across browsers without any backend change, and is saved through the existing profile save path. Task tables, task detail dates, time logs, comment short dates, chat and news feed day headers honour it via the new formatDisplayDate, formatShortDate and formatVerboseDate helpers. CSV exports keep the ISO format. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problems
YYYY-MM-DDtables,MM/DDcomment dates, "August 26" day headers) with no way to getDD/MM/YYYYor "26 August" (fixes Ability to display non-US day/date format #936)Solutions
YYYY-MM-DDdefault,DD/MM/YYYY,MM/DD/YYYY), persisted in thePerson.dataJSONB field through the existing profile save path — same pattern as the 12-hour clock PR for Option for 12-hour time #1929, including the intentional shareddatapassthrough inupdatePerson(src/store/api/people.js) so both branches merge cleanlyformatDisplayDate,formatShortDateandformatVerboseDatehelpers insrc/lib/time.js, exposed throughformatListMixin/useFormat()anduseTime(), applied to task tables (task page, task lists, todos), time logs, comment short dates, entity chat and news feed day headers, and the timesheet header — storage, API and CSV export formats stay ISO