-
-
Notifications
You must be signed in to change notification settings - Fork 35
Define time zone values and conversions #1078
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
There was a problem hiding this 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
I've edited the text a bunch following the conversations around this, hopefully incorporating all of the concerns that have been raised. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
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?