-
-
Notifications
You must be signed in to change notification settings - Fork 776
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
2019-03-22 20:18:42 +0100 interpreted as a string #477
Comments
This package is about yml standard, not about jekyll. If you think js-yaml does not conform spec, please give URL to spec details. Also, reference implementation is pyyaml, if you need to compare. |
Just found this and I've got to say, the spec is way to ambiguous on its definition of timestamps. YAML 1.2 §10.1. Failsafe Schema doesn't actually provide any guidance about what to do with Example 2.22 Timestamps even though it's implied that it shouldn't need an explicit tag. As an editor of other specs, I'd call this a spec bug, not just an implementation one. So congrats, you're both right! I'm inclined to say we should defer to RFC 3339 Date and Time on the Internet: Timestamps §5.6 Internet Date/Time Format, which covers the
to instead have:
But then we don't either allow So I guess I'm off to speak with the editors! |
Ah, looks like this example is likely to be removed: yaml/yaml-spec#268 |
2019-03-13 20:18:42 +0000
is a date format considered valid in Jekyll, when switching to 11ty, it's not. (see: 11ty/eleventy#413 (comment))space separated: 2001-12-14 21:59:43.10 +0000
returns a string on https://nodeca.github.io/js-yaml/http://www.yamllint.com/ will add a colon after parsing:
2019-03-13 20:18:42 +00:00
The text was updated successfully, but these errors were encountered: