-
-
Notifications
You must be signed in to change notification settings - Fork 530
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
Decoder: support all three kinds of TOML dates #96
Comments
Since the issue description is about TOML 0.4.0 dates specifically, I have changed the issue title. (I'll make a meta-issue or milestone for 0.4.0 later, and take stock of all the missing features.) |
Closed
cespare
added a commit
that referenced
this issue
Apr 26, 2016
cespare
added a commit
that referenced
this issue
Apr 26, 2016
mitszo
pushed a commit
to accense/toml
that referenced
this issue
Jul 19, 2016
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently datetime is having an issue with being able to be rendered as in the v0.4.0 spec. If you use a time that does not use UTC (e.g. doesn't have a 'Z' at the end) you get a failure.
1979-05-27T07:32:00Z will convert properly but 1979-05-27T07:32:00-08:00 will not.
I hazard a guess that this ties to the parse.go mapping Datetime
Is this change in the works or does this need to be started on? I'd be glad to help get this worked in. The encode.go appears to need a change as well to have encoding be able to use UTC or non-UTC based time.
If you have any recommendations on this, I may have time to work a bit on this later this weekend. This lack of support blocks movement forward on another project that relies on this library.
The text was updated successfully, but these errors were encountered: