You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have removed unique implicit typing rules and have updated these rules to align them with JSON's productions. In this version of YAML, boolean values may be serialized as “true” or “false”; the empty scalar as “null”.
yaml.v2 is supporting YAML 1.1, but yaml.v3 implements YAML 1.2; hence we should use yaml.v3
The text was updated successfully, but these errors were encountered:
The "norway problem" was popularized from blog posts like https://hitchdev.com/strictyaml/why/implicit-typing-removed/
In YAML 1.1 there is an "implicit typing" feature that converts
no
,yes
,YES
,NO
etc. literals totrue
orfalse
:See the attached slides for a practical example of how unintuitive this is
This is luckily fixed in YAML 1.2:
yaml.v2
is supporting YAML 1.1, butyaml.v3
implements YAML 1.2; hence we should useyaml.v3
The text was updated successfully, but these errors were encountered: