[persons] Add display preference fields to the person model#1160
Merged
frankrousseau merged 2 commits intoJul 13, 2026
Conversation
Two per-user display preferences surfaced in the Kitsu profile page: an opt-in 12-hour clock and the format used for displayed dates. Both are first-class person fields, validated on creation and update, so they follow the user across browsers and stay editable by the person on their own profile. Existing rows read as NULL and the clients fall back to the 24-hour clock and the ISO date format. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
frankrousseau
force-pushed
the
add-person-display-preferences
branch
from
July 13, 2026 08:36
0d5d87a to
7e37f97
Compare
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
1 participant
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.
Problem
dataJSONB blob, unvalidated and clobber-proneSolution
use_12_hour_clock(boolean, default false) anddisplay_date_format(string, defaultYYYY-MM-DD) to the person model, editable by each person on their own profiledisplay_date_formatvalues (outsideYYYY-MM-DD,DD/MM/YYYY,MM/DD/YYYY) with a 400 on creation and update