Status: Open (View Workflow)
writeYaml encodes null values as "null". That's only legal in English according to [the YAML specification|https://yaml.org/type/null.html,] and some processors like Perl's YAML::Syck don't deal with it well. It would be most portable if the canonical representation was used: "~". Although the empty "" or shorthand "!!null" would probably also be good.
I think this could be fixed by a custom Representer class that sets the nullRepresenter to use "~" instead of "null", although arguably this should be fixed in the RepresentNull class itself. I don't see any utility in using "null" over "~".
As Andrey said in the SnakeYAML PR, null is the new canonical representation in YAML 1.2, https://yaml.org/type/null.html is for 1.1. And also YAML::Syck recommends setting ImplicitTyping first thing in its README to support the 1.2 changes like null. So maybe this should just be closed.
Also filed https://bitbucket.org/asomov/snakeyaml/pull-requests/5/dump-null-in-the-canonical-form-instead-of