Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Backslashes in unquoted values break parsing #11

Open
phmarek opened this issue Dec 1, 2020 · 0 comments
Open

Backslashes in unquoted values break parsing #11

phmarek opened this issue Dec 1, 2020 · 0 comments

Comments

@phmarek
Copy link

phmarek commented Dec 1, 2020

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!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant