Dates are written with spaces

[ArthurClemens]

Given a resource struct:

[
  %{
    inserted_at: ~U[2022-07-31 14:48:48.000000Z]
  }
]

The YAML output is:

- inserted_at:
    2022-07-31 14:48:48.000000000 Z

When reading this data back in the application, this is not directly usable to create dates with.

For comparison, Jason encodes this as:

[
  {
    "inserted_at": "2022-07-31T14:48:48.000000Z"
  }
]

which can directly be read using DateTime.from_iso8601()

[jlgeering]

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

current implementation returns a valid timestamp but not in the canonical format => probably better to switch

would require a major version bump => @mruoss what do you think?

[mruoss]

Yes thanks. Was about to check on yaml.org. Maybe we should have an issue template whwere it asks to point to official doc.

So yes, according to doc, the current version is valid YAML but not canonical. Should it be? And yes, would be a major version. And not adapted to the 1.x version.

[mruoss]

Ooops, wrong button, sorry.

[jlgeering]

@mruoss for now, I'm would opt to not make this configurable (wait for a concrete need to add some form of DateTime format option / param)

[mruoss]

@jlgeering Make what configuratble? The output format? I would not make that configurable...

[jlgeering]

@joerichsen FYI this change might impact you

[joerichsen]

I added the PR with DateTime support in order to read YAML stored in strings in our database, where data is stored by a Ruby on Rails application.

So I just added the same format as Ruby stored it in in the PR.

But I just checked and it seems like Ruby is able to read the canonical format just fine as well, so I think that using the canonical format instead makes more sense 👍

[mruoss]

Perfect. Thanks for your heads up @joerichsen.