3 ms·

> This assumption was discovered Did you read the spec? Or did you just start using it assuming you knew how it worked? Whatever generated that clearly wasn't

> This assumption was discovered Did you read the spec? Or did you just start using it assuming you knew how it worked? Whatever generated that clearly wasn't serializing its data using a library, or it would have converted the type into the correct format.

baz00 3y ago
It was somewhere in the middle of a helm chart we imported. So we're building on the shoulders of stuff no one knows how to use.
- chrsig 3y ago
  Yeah, helm is...interesting. it's just a gnarly yaml -> template -> yaml cycle. it's better than nothing for the problem it solves....but god, there's gotta be a better way.
  - ElectricalUnion 3y ago
    Just use JSON for everything that is supposed to accept YAML, and rely on the fact that the entirety of JSON is somehow a subset of YAML and that most YAML never actually needs the "features" of YAML. At least with JSON, tooling can help you find invalid syntax in the middle of your file. And JSON tooling/libraries (compared to YAML tooling/libraries) are usually faster, easier to use, have less bugs and present less incompatibilities between themselves most of the time.
paulddraper 3y ago
Could be more specific about what part of the 60+ page YAML spec you have in mind? https://yaml.org/spec/1.2.2 https://yaml.org/spec/1.2.2
PH95VuimJjqBqy 3y ago
There's always an assumption that if you do things perfect you'll never run into issues. But it's not unreasonable to expect 07 and 08 to work consistently.
lolinder 3y ago
> Whatever generated that clearly wasn't serializing its data using a library Wow, you couldn't ask for a stronger condemnation than that for YAML as a configuration language. "You clearly weren't using a library to write your config file". In the world I live in, config file formats exist to be written and read by humans. Serialization formats exist to be generated by libraries.
- 8n4vidtmkvmk 3y ago
  Not to mention YAML itself purports to be human friendly. Otherwise the config files would have been JSON or something else.

baz00 3y ago

It was somewhere in the middle of a helm chart we imported. So we're building on the shoulders of stuff no one knows how to use.

chrsig 3y ago
Yeah, helm is...interesting. it's just a gnarly yaml -> template -> yaml cycle. it's better than nothing for the problem it solves....but god, there's gotta be a better way.
- ElectricalUnion 3y ago
  Just use JSON for everything that is supposed to accept YAML, and rely on the fact that the entirety of JSON is somehow a subset of YAML and that most YAML never actually needs the "features" of YAML. At least with JSON, tooling can help you find invalid syntax in the middle of your file. And JSON tooling/libraries (compared to YAML tooling/libraries) are usually faster, easier to use, have less bugs and present less incompatibilities between themselves most of the time.

paulddraper 3y ago

Could be more specific about what part of the 60+ page YAML spec you have in mind? https://yaml.org/spec/1.2.2 https://yaml.org/spec/1.2.2

PH95VuimJjqBqy 3y ago

There's always an assumption that if you do things perfect you'll never run into issues. But it's not unreasonable to expect 07 and 08 to work consistently.

lolinder 3y ago

> Whatever generated that clearly wasn't serializing its data using a library Wow, you couldn't ask for a stronger condemnation than that for YAML as a configuration language. "You clearly weren't using a library to write your config file". In the world I live in, config file formats exist to be written and read by humans. Serialization formats exist to be generated by libraries.

8n4vidtmkvmk 3y ago
Not to mention YAML itself purports to be human friendly. Otherwise the config files would have been JSON or something else.