Repository navigation
Conversation
Dates are always displayed in UTC, so users in other time zones have to convert them mentally. Hovering a UTC date now shows it in the browser's local time and locale via a native title tooltip, in data browser cells, the edit row dialog, jobs, config history, push certs and key expiry.
|
🚀 Thanks for opening this pull request! We appreciate your effort in improving the project. Please let us know once your pull request is ready for review. Tip
Note Please respond to review comments from AI agents just like you would to comments from a human reviewer. Let the reviewer resolve their own comments, unless they have reviewed and accepted your commit, or agreed with your explanation for why the feedback was incorrect. Caution Pull requests must be written using an AI agent with human supervision. Pull requests written entirely by a human will likely be rejected, because of lower code quality, higher review effort and the higher risk of introducing bugs. Please note that AI review comments on this pull request alone do not satisfy this requirement. Our CI and AI review are safeguards, not development tools. If many issues are flagged, rethink your development approach. Invest more effort in planning and design rather than using review cycles to fix low-quality code. |
Pull Request
Issue
Dates are always displayed in UTC. Users in other time zones have to convert values like
updatedAtto their local time in their head, which gets more error-prone because of daylight saving time.Approach
Hovering a UTC date now shows the same moment in the browser's local time zone and locale, using a native
titletooltip (Date.prototype.toLocaleString()). The displayed text and copied values stay UTC, so existing behavior doesn't change.Example (browser in Europe/Berlin, de-DE):
Applied everywhere
dateStringUTCis rendered:Not changed: copy rows to clipboard in the data browser (copied text, nothing to hover).
Tasks
Summary by CodeRabbit
New Features
Tests