5 jsonreader should not allow unescaped control characters u+0000 through u+001f in strict mode #18
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
…ntrol characters (U+0000 through U+001F) and throw exceptions.
# Conflicts: # gson/src/main/java/com/google/gson/stream/JsonReader.java
…ntrol characters (U+0000 through U+001F) and throw exceptions.
…cter handling in strict mode and moved the implementation to nextQuotedValue
…cter handling in strict mode and moved the implementation to nextQuotedValue
…ntrol-characters-u+0000-through-u+001f-in-strict-mode
…-not-allow-unescaped-control-characters-u+0000-through-u+001f-in-strict-mode # Conflicts: # gson/src/main/java/com/google/gson/stream/JsonReader.java
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.
This PR implements the change and adds one test for testing the handling of unescaped control characters in strict mode, closes #11