Handle UTF-16 surrogate pairs in WAJsonParser #1341
Merged
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
adriaon
reviewed
Sep 1, 2022
repository/Seaside-Tests-JSON.package/WAJsonParserTest.class/instance/testNonBmpCodePoints.st
Outdated
Show resolved
Hide resolved
adriaon
reviewed
Sep 1, 2022
repository/Seaside-Tests-JSON.package/WAJsonParserTest.class/instance/testNonBmpCodePoints.st
Outdated
Show resolved
Hide resolved
…here a lowSurrogate value would be the first surrogate in the string
|
@marschall I added a testcase and also fixed the case where a low surrogate would be passed as the first (or only one) of the pair. See c1d311e |
jbrichau
previously approved these changes
Sep 10, 2022
Thanks a lot. I changed the formatting and structure a little so that it is a bit easier to understand for me. I hope you concur. |
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.
Fixes #1340