fix: Use compatibility list when checking for timezone - #1229
Merged
Merged
Conversation
blizzz
approved these changes
Sep 9, 2026
blizzz
left a comment
blizzz
left a comment
Member
There was a problem hiding this comment.
Apart of the syntax error that is
Intl.DateTimeFormat().resolvedOptions().timeZone might return some legacy timezone like Europe/Kiev instead of Europe/Kyiv Signed-off-by: Carl Schwan <carl@carlschwan.eu>
CarlSchwan
force-pushed
the
work/carl/timezone
branch
from
September 10, 2026 11:41
a681a7a to
4f6b512
Compare
CarlSchwan
enabled auto-merge
September 10, 2026 11:42
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
2 participants
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.
Intl.DateTimeFormat().resolvedOptions().timeZone might return some legacy timezone like Europe/Kiev instead of Europe/Kyiv
Fix #1227
🤖 AI (if applicable)