YAML 1.2 fixed this making booleans just true/false and it's a real shame that a lot of things still use 1.1
I’m sure Christopher True and Robert False really appreciate that “fix”.
So true. Your comment made my day.
I don't like NO as a boolean literal (mostly because it's also an ISO country code), but there's only one right way to parse it in a YAML 1.1 document. It was a mistake to apply the 1.2 rules to 1.1 documents and issue a "warning" about incorrect output, rather than require rejecting the document if the 1.1 rules aren't implemented.
I'd also like "Sweet" to be true and "Stink" to be false.
That's why StrictYAML always interprets as string unless there's a schema. Cuts out the surprise type conversions.