Handle escaping of the control character #73
Merged
Conversation
This file contains hidden or 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
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.
I've added the ability to handle an escape character when the control is a single
Characterin length.I've also added a value to
Special.stringsto make sure that the parser won't fall back to interpreting the file as anNSDictionary. This tests for a case where previously the parser would complete successfully, but drop the quoted value. A value such as\"http://\" or \"https://\"would be parsed as[.key("quoted"), .equal, .value("\\"), .message("\\\" or \\\"https://\\\"\";")]due to the parser encountering a//and attempting to read a comment. Since values don't get added to the results until a semicolon is encountered, it would cause the quoted string to be dropped.