fix(parser): Ensure error spans are valid for escape sequences #715
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
After a `\` in a string, the parser consumes the next character and then validates it. If the validation fails, it means that the parser is now pointing to the next byte after it which could be within a byte sequence. We likely want to fix up some of these cases so errors point to the right thing but in the mean time, we should make sure this doesn't produce a bad span.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
After a
\in a string, the parser consumes the next character and then validates it.If the validation fails, it means that the parser is now pointing to the next byte after it which could be within a byte sequence.
We likely want to fix up some of these cases so errors point to the right thing but in the mean time, we should make sure this doesn't produce a bad span.