Official, meaningful tooling for yaml also doesn't exist. Parsing and emitting yaml does nothing for anyone until you can actually extract structures from the format.
The full yaml standard is also full of features no one ever actually uses in practice, but if you don't implement it, you are thusly not compliant with the specification.
If you read it, you'd go, "Wow, you can do that?" and "That's bad that you can do that."
And by YAML, some libraries implement YAML 1.1, some others implement YAML 1.2, and by YAML 1.2 they actually mean YAML 1.2 core schema. And often they implement that poorly.
So it doesn't help that:
* there is YAML 1.1 and YAML 1.2, and you need to know which one you want to use
* there is this thing called "core schema" and it's possible to use other schemas, but nobody seems to care
* the spec itself is complex, and hard to implement well
Comments
Official, meaningful tooling for yaml also doesn't exist. Parsing and emitting yaml does nothing for anyone until you can actually extract structures from the format.
The full yaml standard is also full of features no one ever actually uses in practice, but if you don't implement it, you are thusly not compliant with the specification.
If you read it, you'd go, "Wow, you can do that?" and "That's bad that you can do that."
There is a parser and producer for yaml in all the major languages. I mean, even
what level of tooling do you mean?And by YAML, some libraries implement YAML 1.1, some others implement YAML 1.2, and by YAML 1.2 they actually mean YAML 1.2 core schema. And often they implement that poorly.
So it doesn't help that:
* there is YAML 1.1 and YAML 1.2, and you need to know which one you want to use
* there is this thing called "core schema" and it's possible to use other schemas, but nobody seems to care
* the spec itself is complex, and hard to implement well
https://github.com/mikefarah/yq