Only 1.1. Which everybody has been fiercely clinging onto since 2009, because YAML 1.2 did not seem to consider it a problem that they broke backwards compatibility on that behavior. So now the only way to keep existing YAML files working is for us all to keep pretending YAML 1.2 does not exist.
Go right ahead and tell me what the YAML version is and what is the type of somekey is. Oh that’s right, it’s impossible, because the versioning is entirely up to the serializers for some godforsaken reason.
Only 1.1. Which everybody has been fiercely clinging onto since 2009, because YAML 1.2 did not seem to consider it a problem that they broke backwards compatibility on that behavior. So now the only way to keep existing YAML files working is for us all to keep pretending YAML 1.2 does not exist.
“Broke backwards compatibility”
Brother, what do you think versioning is for?
Which versioning???
somekey: yesGo right ahead and tell me what the YAML version is and what is the type of
somekeyis. Oh that’s right, it’s impossible, because the versioning is entirely up to the serializers for some godforsaken reason.Ow! My semver.