-
Notifications
You must be signed in to change notification settings - Fork 50
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
Why does library discard UTC offsets? #112
Comments
+1 because of this limitation you need a separate field to transmit the timezone info if you want to display the date in some specific timezone. UTC offsets are part of the RFC 3339 spec so there's no reason not to support it. |
I can see the case for both normalization and for wanting to communicate dates in their native timezones to applications. Maybe this calls for 2 types? |
This causes problems for me because the Date |
+1 I would like to be able to allow offsets. |
Where an RFC 3339 compliant date-time string has a time-zone other than UTC, it is shifted to UTC. For example, the date-time string "2016-01-01T14:10:20+01:00" is shifted to "2016-01-01T13:10:20Z".
Would there be consideration to add a type that allows offsets?
The text was updated successfully, but these errors were encountered: