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
personally I prefer to use quotes for string in YAML, rather than raw strings, to keep avoid confuses around number, like this:
app:
version: 1.2.3 # => stringpg:
version: 15.2# => edited by human and now its number, but unexpected...
in js-yaml, this can be done with forceQuotes option for yaml.dump(), but this also disables |- syntax.
app:
version: '1.2.3'# this is string, really clearstartup: "#!/bin/bash\n# doing something\n# also doing something..."# ... hard to read
since | defines they are always string (like quotes does), it would be good to have option to also allow their (aka just simply disallows implicit string literal)
personally I prefer to use quotes for string in YAML, rather than raw strings, to keep avoid confuses around number, like this:
in js-yaml, this can be done with
forceQuotes
option foryaml.dump()
, but this also disables|-
syntax.since
|
defines they are always string (like quotes does), it would be good to have option to also allow their (aka just simply disallows implicit string literal)Expected Result:
The text was updated successfully, but these errors were encountered: