YAML bare tilde value must be quoted about oh-my-posh HOT 6 CLOSED

@Bilge it's the destination that matters, not the journey. Or something like that. Who knows.

from oh-my-posh.

@Bilge as we rely on a third party parser, I'm going to see if we can solve this, or if they have a bug. Thanks for reporting this one.

from oh-my-posh.

@Bilge this is an annoying one. I understand the request and I can fix it by adjusting the parser BUT, it's going against the YAML spec this way. The parser has no way to quote all strings, it decides based on the content which could imply that the following JSON export:

{ "key": "~" }

can originate from the following YAML:

key: ~

and be entirely correct.

So, I will hack this in for oh-my-posh specifically, but it's a project specific hack.

from oh-my-posh.

Incorrect. The following YAML:

key: ~

Is equivalent to the following JSON:

{"key": null}

This is documented in the YAML parser spec I previously linked. So no, this is not a project-specific hack, it's correctly interpreting the spec for any use. In particular:

null | Null | NULL | ~ tag:yaml.org,2002:null

Note that the ~ is listed as a valid representation of null.

from oh-my-posh.

@Bilge so, from JSON, and any other model that doesn't have a magical notation for ~, it needs to always parse to "~". In that case my hack is actually a fix.

from oh-my-posh.

Yes, you arrived at the good solution, just possibly for the wrong reasons. 🤷🏻‍♂️

from oh-my-posh.