Skip to content

feat(web): show raid times in each viewer's timezone - #15

Merged
joshchen-dev merged 1 commit into
mainfrom
claude/great-shannon-b4y5vi
Oct 6, 2026
Merged

joshchen-dev merged 1 commit into
mainfrom
claude/great-shannon-b4y5vi

Conversation

@joshchen-dev

@joshchen-dev joshchen-dev commented Oct 6, 2026 •

Copy link
Copy Markdown
Owner

Summary

The availability grid showed every date in the team's timezone, so a member abroad had to convert the times themselves.

  • Grid column headers show the day and time in the viewer's timezone.
  • When the team's wall-clock time reads differently, a muted line beneath shows it. Examples: 21:00 Tokyo, or Wed 7 21:00 Tokyo when the day differs too. It is hidden when the viewer is in the team's timezone.
  • The "Next timetable posts …" line and the date toasts follow the viewer's timezone too.
  • The schedule editor stays in team time, because that is what it configures. The landing page's sample grid stays fixed.
  • Playwright now pins the browser to Asia/Tokyo, the fixtures' team timezone, so existing assertions are deterministic. Individual tests override it.

Release v0.0.14.

Tests

  • Playwright:
    • a Los Angeles viewer sees Wed 7 · 05:00 · 21:00 Tokyo
    • an Auckland viewer sees Thu 8 · 01:00 · Wed 7 21:00 Tokyo
    • a Tokyo viewer sees no repeated team time
  • npm run check, format:check, build, and Playwright (23 passed, 1 desktop-skipped phone test) all pass locally.

The availability grid showed every date in the team's timezone, so a
member abroad had to convert times themselves. Dates and times now use
the viewer's timezone, with the team's time beneath when it reads
differently ("Wed 7 21:00 Tokyo" when the day differs too). The "next
timetable posts" line follows the viewer as well; the schedule editor
stays in team time because that is what it configures.

Release v0.0.14.
@joshchen-dev
joshchen-dev merged commit 7350875 into main Oct 6, 2026
1 check passed
@joshchen-dev
joshchen-dev deleted the claude/great-shannon-b4y5vi branch October 6, 2026 14:06
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