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
http://yaml.org/spec/1.1/#id907281
Question marks aren't mentioned as special inside of plain scalars here.
To be an indicator for an explicit key, it must be at the beginning and followed by a space or newline.
The following cases should be allowed:
[foo?bar]
[foo ? bar]
This would allow [ http://example/query?a=b ].
Even this one should be allowed, but it would potentially break existing code:
[?foo]
# same as
["?foo"]
# but currently parsed as
[? foo ]
The Spec:
The first plain character is further restricted to avoid most indicators as these
would cause ambiguity with various YAML structures. However, the first character
may be “-”, “?” or “:” provided it is followed by a non-space character.
[157] ns-plain-first-char(c) ::= ( ns-plain-char(c) - c-indicator )
| ( ( “-” | “?” | “:” ) ns-plain-char(c) )
The text was updated successfully, but these errors were encountered:
See also yaml/libyaml#105
http://yaml.org/spec/1.1/#id907281
Question marks aren't mentioned as special inside of plain scalars here.
To be an indicator for an explicit key, it must be at the beginning and followed by a space or newline.
The following cases should be allowed:
This would allow
[ http://example/query?a=b ]
.Even this one should be allowed, but it would potentially break existing code:
The Spec:
The text was updated successfully, but these errors were encountered: