@mhoye
I doubt anyone is willing to do the work but there would be a lot of value in formalizing the safe subset of yaml (block syntax, json interoperability, multiline strings, comments) and gets rid of the weird bits (cross references, tags, "no", etc)
On the other hand "everything is a string unless it looks like a number, boolean or null" manages to be both great for usability and a great footgun and I don't know how to square that circle.
@tetron I think that we as an industry need to start getting really explicit about what "usability" means, particularly in those cases where it clearly means "somewhat robust in the face of neglect and negligence."
@mhoye @tetron as I mentioned elsewhere YAML is like a mid century industrial machine. It does its job but it will take your arm off if you're not careful.
Someone decided that we needed a schemaless generic configuration format and we got exactly that.
The implementer in this case didn't check the incoming data.. They fixed the cause of the problem (the unquoted hash) but afaict they don't implement a data check to insure it doesn't happen again even if the workflow changes.
