-
Notifications
You must be signed in to change notification settings - Fork 1
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
feat: allow exact values #4
Conversation
This just disables the inline comment escaping
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks great, thanks! Can we update the README with some basic details about this new exactValue
option please?
I also wonder if it might be better to simply only look at So:
would parse as |
Would we want to check for spaces all around the character or just after it? IE: where we'd stop parsing on the space so it'd just come out as |
There seems to be some consensus (as much as you get can get for |
Yeah makes sense to me. It's easy enough in the parser to check for whitespace around the comment character. |
This just disables the inline comment escaping