Invalid Date format

[DirtyF]

Given I import a blog post from Jekyll
When I run eleventy
Then  an error is raised: `Error: date front matter value (2018-11-20 16:33 +0100) is invalid`

According to https://www.11ty.io/docs/dates/, it's not valid. 😞

That means I have to change the date of all my existing posts?

[zachleat]

Where did this date format come from? It’s not a valid YAML or UTC String?

[DirtyF]

According to https://yaml.org/type/timestamp.html:

a more relaxed format is also supported for enhanced readability, using white space separation.

[zachleat]

Oh interesting. Are you sure those aren’t accidentally strings? Doesn’t look like YAML tries to parse them at all, as that error comes from a fallback condition where Luxon tries to parse the date string: https://github.com/11ty/eleventy/blob/master/src/Template.js#L613

[zachleat]

Can you attach an example of the front matter that’s failing?

[DirtyF]

Here is an example of a Forestry output, leading to the same error:

---
subtitle: New doc page
date: 2019-03-13 20:18:42 +0000
tags:
- docs
---

[zachleat]

Alright I dove in a bit deeper on this and I think it’s a js-yaml bug. We use gray-matter which uses js-yaml.

They have a live demo here: https://nodeca.github.io/js-yaml/

Your example returns a string. The following formats do work:

For comparison YAMLlint thinks your date format is valid, albeit it corrects the formatting by adding a colon to 00:00:

Can you file this upstream and provide a link back? https://github.com/nodeca/js-yaml
http://www.yamllint.com/

[zachleat]

Hmm, sorry that was closed—but he may be right.

Note that the string result does match the pyyaml implementation:

Here’s the relevant time zone bit from the YAML 1.1 spec (I wasn’t able to actually find this in the YAML 1.2 spec? That might be worth digging deeper into)

(([ \t]*)Z|[-+][0-9][0-9]?(:[0-9][0-9])?)? # (time zone)

Note that if the four digit format is used, it requires the :.

[zachleat]

Also note that in the discussion above “a more relaxed format is also supported for enhanced readability, using white space separation” refers to the whitespace between the time and the time zone, not whitespace between the timezone hours and timezone minutes.

space separated: 2001-12-14 21:59:43.10 -5

Sorry 😲

[zachleat]

Worth noting that feature request #335 may give you an easier out here? Not sure. Might let you avoid having to update all of your data.

[wangzhankun]

Hello, I run into the same trouble,

---
date: 2023-12-08 17:02:02
tags:
  - 用户态驱动
  - OS/Linux
dg-publish: "true"
---

What is wrong with the formatter?
The issue I posted is at oleeskild/digitalgarden/issues/236