Skip to content

feat: Show local time on hover over UTC date values - #3507

Open
3011felix wants to merge 1 commit into
parse-community:alphafrom
3011felix:feat/date-local-time-tooltip
Open

3011felix wants to merge 1 commit into
parse-community:alphafrom
3011felix:feat/date-local-time-tooltip

Conversation

@3011felix

@3011felix 3011felix commented Oct 25, 2026 •

Copy link
Copy Markdown

Pull Request

Issue

Dates are always displayed in UTC. Users in other time zones have to convert values like updatedAt to 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 title tooltip (Date.prototype.toLocaleString()). The displayed text and copied values stay UTC, so existing behavior doesn't change.

Example (browser in Europe/Berlin, de-DE):

Displayed Tooltip
15 Jan 2026, 9:00:00 UTC 15.1.2026, 10:00:00
15 Jul 2026, 9:00:00 UTC 15.7.2026, 11:00:00

Applied everywhere dateStringUTC is rendered:

  • Data browser Date cells
  • Edit row dialog (CreatedAt / UpdatedAt)
  • Jobs status table (created / finished)
  • Jobs form "will run on …" footer
  • Config parameter change history dropdown
  • Push certificate and key expiry (FormTable notes)

Not changed: copy rows to clipboard in the data browser (copied text, nothing to hover).

Tasks

  • Add tests

Summary by CodeRabbit

  • New Features

    • Date and time values across browser data, certificates, account keys, configuration history, and job details now show a localized date and time when hovered. Existing UTC-formatted values remain visible.
    • Copying dates from browser date cells continues to use the UTC-formatted value.
  • Tests

    • Added coverage for the browser date’s localized hover text and UTC display.

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.
@parse-github-assistant

Copy link
Copy Markdown

🚀 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

  • Keep pull requests small. Large PRs will be rejected. Break complex features into smaller, incremental PRs.
  • Use Test Driven Development. Write failing tests before implementing functionality. Ensure tests pass.
  • Group code into logical blocks. Add a short comment before each block to explain its purpose.
  • We offer conceptual guidance. Coding is up to you. PRs must be merge-ready for human review.
  • Our review focuses on concept, not quality. PRs with code issues will be rejected. Use an AI agent.
  • Human review time is precious. Avoid review ping-pong. Inspect and test your AI-generated code.

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.

@coderabbitai

coderabbitai Bot commented Oct 25, 2026 •

Copy link
Copy Markdown

Review in Change Stack →

No actionable comments were generated in the recent review.

Recent review info
Run configuration
  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: Organization UI
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: 6462b15f-b5a6-4287-89b4-db4fed7586b2
Commits

Reviewing files that changed from the base of the PR and between 13ecc66 and 1742393.

Files selected for processing: 8
  • src/components/BrowserCell/BrowserCell.react.js
  • src/components/PushCerts/CertsTable.react.js
  • src/dashboard/Account/AccountOverview.react.js
  • src/dashboard/Data/Browser/EditRowDialog.react.js
  • src/dashboard/Data/Config/ConfigDialog.react.js
  • src/dashboard/Data/Jobs/Jobs.react.js
  • src/dashboard/Data/Jobs/JobsForm.react.js
  • src/lib/tests/BrowserCell.test.js

Included review availability: This review used your included allowance. Your plan provides up to 8 included reviews per hour; 6 remain after this review.

Walkthrough

Date values retain UTC-formatted visible text and now expose locale-formatted values in tooltips across browser cells, certificates, account keys, record history, and job views. BrowserCell also retains the UTC-formatted date as its copyable value.

Changes: Localized Date Display

Layer / File(s) Summary
BrowserCell date display and copy value
src/components/BrowserCell/BrowserCell.react.js, src/lib/tests/BrowserCell.test.js
BrowserCell retains the UTC-formatted date as its copyable value and adds a locale-formatted title. The Date test checks the title and visible text.
Expiration date tooltips
src/components/PushCerts/CertsTable.react.js, src/dashboard/Account/AccountOverview.react.js
Certificate and account key expiration dates retain UTC-formatted display text and add locale-formatted titles.
Record and job timestamp tooltips
src/dashboard/Data/Browser/EditRowDialog.react.js, src/dashboard/Data/Config/ConfigDialog.react.js, src/dashboard/Data/Jobs/Jobs.react.js, src/dashboard/Data/Jobs/JobsForm.react.js
Record history and job timestamps retain UTC-formatted display text and add locale-formatted titles. The finished-time title is undefined when no finish time exists.

Priority: Low

Estimated code review effort: 2 (Simple) | ~10 minutes

Suggested reviewers: mtrezza

Merge Risk: Minimal · up to 17423

The PR adds local-time hover tooltips without changing displayed or copied UTC values.

Pre-merge checks: Passed 7
Check name Status Explanation
Title check Passed The title begins with the required prefix "feat:" and the first letter after the prefix is capitalized ("Show"). It describes the main change: a native tooltip that shows local time when hovering over…
Description check Passed The description explains the problem (dates display only in UTC), the approach (a native title tooltip using Date.prototype.toLocaleString(), with displayed and copied values kept in UTC), and lists e…
Docstring Coverage Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 8…
Linked Issues check Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check Passed Check skipped because no linked issues were found for this pull request.
Security Check Passed No security vulnerability is introduced by the pull request. The changes only add Date.prototype.toLocaleString() results to React title attributes and wrap existing UTC text in React elements. Re…
Engage In Review Feedback Passed No review feedback required engagement. The supplied review data reports zero actionable findings and no CodeRabbit review threads.
Full details: Title check

Explanation

The title begins with the required prefix "feat:" and the first letter after the prefix is capitalized ("Show"). It describes the main change: a native tooltip that shows local time when hovering over UTC date values, which matches the changeset across the date-rendering components.

Full details: Description check

Explanation

The description explains the problem (dates display only in UTC), the approach (a native title tooltip using Date.prototype.toLocaleString(), with displayed and copied values kept in UTC), and lists every affected location, plus an example table. It also marks the Add tests task as done. The template's Issue and Approach sections are filled in. The template's documentation task is not checked and the author does not say whether documentation was updated, and the Issue section does not link an issue. These are minor gaps that do not make the description incomplete.

Full details: Docstring Coverage

Explanation

No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 8 files.

Full details: Security Check

Explanation

No security vulnerability is introduced by the pull request. The changes only add Date.prototype.toLocaleString() results to React title attributes and wrap existing UTC text in React elements. React escapes these values, and the diff adds no raw HTML sinks, script execution, URL handling, or security-sensitive data flow. FormTable and Dropdown render the new elements as normal React children.

Finishing Touches
🧪 Generate unit tests (beta)
  • Create a new PR
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Comment @coderabbitai help to get the list of available commands.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant