3 ms·
A new spec version doesn’t mean we stop having the problem. E.g. kubernetes wrote about solving this only five months ago[1] and by moving from yaml to kyaml,
by merelysounds 9mo ago
A new spec version doesn’t mean we stop having the problem.
E.g. kubernetes wrote about solving this only five months ago[1] and by moving from yaml to kyaml, a yaml subset.
[1]: https://kubernetes.io/blog/2025/07/28/kubernetes-v1-34-sneak-peek/ https://kubernetes.io/blog/2025/07/28/kubernetes-v1-34-sneak...
- Y-bar 9mo agoThe 1.1 spec was released about _twenty_ years ago, I explicitly used the word _implemented_ for a reason. As in: Our Yaml lib vendor had begun officially supporting that version more than ten years ago.
- merelysounds 9mo agoNote that you reference 1.1, I think that version still had the norway behavior.
- Y-bar 9mo ago1.1 partially fixed it, so that strings (quoted ”no”) did not become Boolean false. 1.2 strengthened it to remove unquoted no from list of tokens which could be interpreted as Boolean false.
- merelysounds 9mo ago> 1.1 partially fixed it, so that strings (quoted ”no”) did not become Boolean false. Do you have a source? Afaik v1.1 didn’t introduce such a change, v1.0 specified the same behavior for quoted strings, i.e. in v1.0 a quoted “no” would remain a string “no” as well.