Eemeli Aro
Eemeli Aro
We also need to reserve at least `@` (attributes) and `#` & `/` (markup), and almost certainly `=` as it's used in options and attributes. I would be much more...
> Reserving '@' is not necessary, because syntactically it can't cause ambiguity in the syntax (an attribute can't be in the same position as a literal). Same for '#' and...
We'll also need to exclude `*` as `unquoted-literal` is also used in variant keys, where `*` is special.
> could we, as WG members, try to keep separate topics in separate issues? Fair point. I'll break this up into three, keeping the options here because that's what you...
> With maps for options, the serialization of a message becomes unstable in languages where maps keys are unordered. This may result in false positives when comparing serialized messages for...
What's the benefit of allowing for an option with no value to be represented in the data model?
@mihnita Why would we want to explicitly preserve option order?
I would not oppose something like the proposed text, but I honestly don't think it's necessary to encourage or require tools to keep source order when parsing and reserialising option...
LRM and RLM are valid `content-char`, so if they show up within a pattern the syntax is completely fine with that. But is this about asking for them to be...
Would using the option `singleQuote: true` work for you? The problematic behaviour is specific to double-quoted scalars, so: ```js YAML.stringify(obj, { singleQuote: true }) ``` ```yaml mystring: '[this is an...