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
I've got a YAML file whose values include backslashes (filenames for Windows).
This seems to irritate the parsing routine immensely; as long as they're not in double quotes ("), I get errors like
ESRAP-LIQUID parsing failed.
Rule-stack : ()
Position : 142
Text right before : yaml
Specific reason: Didn't make it to the end of the text
where byte 142 is within the first header line comments, and the backslashes are about 1000 bytes later on.
When I put " around the c:\Program Files\mozilla firefox\Firefox path, it works as expected.
I'm not sure what the defined behaviour for YAML is; but either the error message should be improved or parsing such unquoted values should be allowed.
The other libraries didn't complain about that, BTW.
Thanks!
The text was updated successfully, but these errors were encountered:
I've got a YAML file whose values include backslashes (filenames for Windows).
This seems to irritate the parsing routine immensely; as long as they're not in double quotes (
"
), I get errors likewhere byte 142 is within the first header line comments, and the backslashes are about 1000 bytes later on.
When I put
"
around thec:\Program Files\mozilla firefox\Firefox
path, it works as expected.I'm not sure what the defined behaviour for YAML is; but either the error message should be improved or parsing such unquoted values should be allowed.
The other libraries didn't complain about that, BTW.
Thanks!
The text was updated successfully, but these errors were encountered: