You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
One interesting question would be how the timeZoneName option should be handled. It seems reasonable to use the IXDTF format (the one we're working with IETF to specify) like 2020-12-25T12:34:56[America/Los_Angeles].
This formatting can also be delegated to Temporal AOs if needed.
It also makes sense to specify in this proposal whether the options bag {timeZoneName: "long"} should assume a full date should be shown like 2020-01-01[America/Los_Angeles], or if only America/Los_Angeles should be returned. I assume the former for backwards compatibility?
The text was updated successfully, but these errors were encountered:
It also makes sense to specify in this proposal whether the options bag {timeZoneName: "long"} should assume a full date should be shown like 2020-01-01[America/Los_Angeles], or if only America/Los_Angeles should be returned. I assume the former for backwards compatibility?
I don't think that's necessarily within scope; the behaviour should match what's used with other locales.
One interesting question would be how the
timeZoneName
option should be handled. It seems reasonable to use the IXDTF format (the one we're working with IETF to specify) like2020-12-25T12:34:56[America/Los_Angeles]
.This formatting can also be delegated to Temporal AOs if needed.
It also makes sense to specify in this proposal whether the options bag
{timeZoneName: "long"}
should assume a full date should be shown like2020-01-01[America/Los_Angeles]
, or if onlyAmerica/Los_Angeles
should be returned. I assume the former for backwards compatibility?The text was updated successfully, but these errors were encountered: