Fix reading strings that contain quotes or open/closed brackets #8
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.
The parsing code did not properly ignore escaped quotes inside strings, which means that a string containing something like a serialized object would be potentially read wrong by switching in and out of being "in string".
next_value
also did not ignore{
and[
that are inside a string, interpreting them as a "child" list or object.This would manifest by returning a
TransientObject
from a string, raisingKeyError
, EOF or a JSON parsing error, or falling into an infinite loop.This PR ignores the special meaning of the first character after a backslash inside a string (outside a string it would not be valid json anyway), and rearranges the parsing code to switch more consistently between in-string and not in-string.