My Day: show the date with the time in 'Updated at'

Merged
BI
1mo ago
+38-7

User description

Follow-up to #3508 (owner-approved request to show the date, not only the time, in the 'Updated at' display).

  • myDayUpdatedAgo (src/components/my-day/my-day-page-parts.tsx): once the data is an hour old, Updated at 14:05 now reads Updated at 14:05, Tue 13 Oct, dated on the work-zone (Perth default) calendar via perthDateOf + formatPerthDay. "just now" / "N min ago" are unchanged.
  • Tests: tests/my-day-updated-ago.test.ts covers the hour boundary, a day-old reading, and Perth-vs-UTC date edges (23:30 and 07:30 Perth).

Local: vitest (my-day-updated-ago, my-day-page.dom) 43/43, eslint, prettier pass. Full typecheck left to CI (local push guard skipped it because another heavy run held the coordinator).

Summary by cubic

Follow-up to #3508: once My Day data is an hour old, "Updated at 14:05" now reads "Updated at 14:05, Tue 13 Oct" so yesterday's data isn't mistaken for today's. Both time and date are derived from the recorded moment in the work zone the page passes in (myDayUpdatedAgo takes the zone with a Perth default), so an earlier clock string can't introduce a mismatch. "just now" and "N min ago" are unchanged.

Bug Fixes

  • When no clock time is recorded, the hour-old case now derives time and date from the recorded moment instead of falling back to "over an hour ago".
  • Tests cover the hour boundary, a day-old reading, Perth-vs-UTC date edges, and formatting in a non-Perth zone.

CodeAnt-AI Description

Show the date and work-zone time for older My Day updates

What Changed

  • Once My Day data is an hour old, its update label includes both the time and date.
  • The time and date come from the same recorded moment in the page’s work zone, even if earlier clock text is missing or outdated.
  • “Just now” and minute-based labels remain unchanged.

Impact

✅ Clearer dates for yesterday’s My Day data
✅ Consistent update times across work zones
✅ Reliable labels when earlier clock text is unavailable

💡 Usage Guide

Checking Your Pull Request

Every time you make a pull request, our system automatically looks through it. We check for security issues, mistakes in how you're setting up your infrastructure, and common code problems. We do this to make sure your changes are solid and won't cause any trouble later.

Talking to CodeAnt AI

Got a question or need a hand with something in your pull request? You can easily get in touch with CodeAnt AI right here. Just type the following in a comment on your pull request, and replace "Your question here" with whatever you want to ask:

@codeant-ai ask: Your question here

This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code.

Example

@codeant-ai ask: Can you suggest a safer alternative to storing this secret?

Preserve Org Learnings with CodeAnt

You can record team preferences so CodeAnt AI applies them in future reviews. Reply directly to the specific CodeAnt AI suggestion (in the same thread) and replace "Your feedback here" with your input:

@codeant-ai: Your feedback here

This helps CodeAnt AI learn and adapt to your team's coding style and standards.

Example

@codeant-ai: Do not flag unused imports.

Retrigger review

Ask CodeAnt AI to review the PR again, by typing:

@codeant-ai: review

Check Your Repository Health

To analyze the health of your code repository, visit our dashboard at https://app.codeant.ai. This tool helps you identify potential issues and areas for improvement in your codebase, ensuring your repository maintains high standards of code health.