Skip to content

Fix time zone canonicalization behaviour in DateTimeFormat test#4453

Merged
ptomato merged 1 commit intotc39:mainfrom
ptomato:canonicalize-timezone
Apr 14, 2025
Merged

Fix time zone canonicalization behaviour in DateTimeFormat test#4453
ptomato merged 1 commit intotc39:mainfrom
ptomato:canonicalize-timezone

Conversation

@ptomato
Copy link
Contributor

@ptomato ptomato commented Apr 12, 2025

As of the Time Zone Canonicalization proposal which is stage 3, the original time zone name should be preserved in Intl.DateTimeFormat .prototype.resolvedOptions.

Add a separate test that uses Temporal.ZonedDateTime.prototype.equals to test the canonicalization behaviour.

@ptomato ptomato requested a review from ryzokuken April 12, 2025 00:02
@ptomato ptomato requested a review from a team as a code owner April 12, 2025 00:02
@ptomato
Copy link
Contributor Author

ptomato commented Apr 12, 2025

cc @justingrant

Copy link
Contributor

@justingrant justingrant left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

@Ms2ger Ms2ger force-pushed the canonicalize-timezone branch from 737b6f0 to 4cfea3f Compare April 14, 2025 15:50
As of the Time Zone Canonicalization proposal which is stage 3, the
original time zone name should be preserved in Intl.DateTimeFormat
.prototype.resolvedOptions.

Add a separate test that uses Temporal.ZonedDateTime.prototype.equals
to test the canonicalization behaviour.
@ptomato ptomato force-pushed the canonicalize-timezone branch from 4cfea3f to ded9215 Compare April 14, 2025 16:27
@ptomato ptomato merged commit 7c4a799 into tc39:main Apr 14, 2025
11 checks passed
@ptomato ptomato deleted the canonicalize-timezone branch April 14, 2025 16:31
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.

4 participants