Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

eemeli
Copy link
Collaborator

@eemeli eemeli commented Jun 8, 2025

This is proposed as a separate change from #1077, as it was not discussed on the call.

The intent with the text updated here is to clarify what happens when the timeZone option is set on a date/time function.

The SHOULD/MAY language that's proposed is intended to allow for an implementation that does not support time zone conversions, which I believe matches the case in JS Temporal.

Is there prior art of local being used as a time zone value as we're proposing, or are there alternatives that other date/time formatters use?

@eemeli eemeli requested review from aphillips and sffc June 8, 2025 06:47
Copy link
Member

@sffc sffc left a comment

Choose a reason for hiding this comment

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

Fallback algorithm seems ok, since it has an out for an implementation that doesn't support time zone conversion

@aphillips aphillips added the functions Issue pertains to the default function set label Jun 30, 2025
@eemeli
Copy link
Collaborator Author

eemeli commented Jul 14, 2025

I've edited the text a bunch following the conversations around this, hopefully incorporating all of the concerns that have been raised.

Copy link
Collaborator

@catamorphism catamorphism left a comment

Choose a reason for hiding this comment

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

LGTM

@eemeli eemeli merged commit cb009b5 into main Jul 21, 2025
1 check passed
@aphillips aphillips deleted the local-is-default branch July 21, 2025 16:55
@eemeli eemeli added this to the LDML 48 milestone Jul 23, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
functions Issue pertains to the default function set
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants