fix: normalize schedule date_utc to ISO 8601 with Z suffix for correct browser timezone conversion#45
Merged
adn8naiagent merged 1 commit intoadn8naiagent:devfrom Mar 16, 2026
Conversation
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
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
The \date_utc\ values in the static schedule JSON files (e.g. \data/seasons/2026/schedule.json) use the format \2026-03-15 07:00:00\ without a timezone indicator. When the frontend receives these values, JavaScript's
ew Date('2026-03-15 07:00:00')\ treats them as local time instead of UTC, so users see raw UTC times instead of their local timezone.
Fix
Normalize \date_utc\ strings in _build_events()\ before returning the response:
This ensures the frontend's \FormatLocalTime()\ function correctly interprets dates as UTC and converts them to the user's local timezone via \ oLocaleTimeString().
Example