Tatu Saloranta

Yeah the problem is that it does really map to `JsonNode` model (nor can I see an easy way to model it). In your case, either "null" key would need...

Correct: Jackson's streaming/token model is based on JSON and there's no `null` key, only `null` values. And `JsonNode`, similarly only `String` keys. YAML and other formats need to be expressed...

I think I am still inclined to prefer empty String as surrogate (and possible make this `YAMLParser.Feature` whether to replace "~" key or not -- since there may well be...

I guess from my end, while I think I understand the issue, I am not sure how to address this at Jackson level. The original request is something I do...

@asomov I think he means round-tripping (read-write), in which something reads YAML with Jackson into, say, `JsonNode`, possibly modifies some parts, than writes out as YAML. If so, "~" as...

As of now, 3.0.0 uses snakeyaml-engine (converted quite a while ago), which, as you say, supports YAML 1.2. I don't really want to have 2 backends for 3.0.0 tho --...

3.0 supports YAML 1.2; 2.x does not and probably won't. Closing.

Supported added for YAML, so will remove `yaml` label. Remains to be supported by `csv`, `properties` and `toml` backends.

No, this cannot be done currently. But this has come up multiple times, and I think we have some existing issues. One big problem is that it is very difficult...

It'd be nice to have test inlined here, instead of as a zip archive. But aside from that yes, there is a problem in using non-XML-name characters in Map keys...