-
Notifications
You must be signed in to change notification settings - Fork 3
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
Refactor string literal escaping #24
Conversation
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.
I think duplicated test are not necessary, it's just change of format, so I believe that 4 people's 👀 would catch the mistake if any.
If you want to keep old tests, feel free, no harm done of course, but please add a comment explaining why are there duplicated tests - could be pretty confusing in the future 😉
Why did you change only some of the tests? I thought that the we want to get rid of all the escaping hell. And I agree with janmisar, it's only a matter of the format and I would prefer to have just the latter |
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.
Thanks for the update. 👍 amazing work!
This PR refactors internal escaping sequences so the code is bit more readable.
We should probably discuss if the "added" tests should be present or not, I didn't want to change older tests so we can be sure we do not create any regression, but still wanted to test the new "syntax" as well. I think more tests even if they test the same thing do not hurt.
Checklist