We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
This issue was originally filed by [email protected]
ISO 8601 allows to define time offsets. Currently the DateTime.parse can't parse a +00 offset. http://en.wikipedia.org/wiki/ISO_8601#Time_offsets_from_UTC
For example DateTime.parse("2012-02-27T14+00:00") won't be parsed as UTC.
DateTime.parse("2012-02-27T14+00:00")
The text was updated successfully, but these errors were encountered:
It's on our TODO list.
Added Duplicate label. Marked as being merged into #1878.
Sorry, something went wrong.
This comment was originally written by [email protected]
Oh okay, I already submitted a small patch improving DateTime.parse
https://codereview.chromium.org/48823005
No branches or pull requests
This issue was originally filed by [email protected]
ISO 8601 allows to define time offsets. Currently the DateTime.parse can't parse a +00 offset.
http://en.wikipedia.org/wiki/ISO_8601#Time_offsets_from_UTC
For example
DateTime.parse("2012-02-27T14+00:00")
won't be parsed as UTC.The text was updated successfully, but these errors were encountered: