keep chop from splitting a trailing surrogate pair - #1770
Open
alhudz wants to merge 1 commit into
Open
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.
StringUtils.chopcuts the last UTF-16 char, so aStringending in a supplementary code point is left holding a lone surrogate.Repro:
chop("x😀"), aStringending inU+1F600.Expected:
"x", dropping the whole trailing code point, the same waychop("a")returns"".Actual:
"x\uD83D", only the low surrogate is removed and a lone high surrogate is left behind (malformed UTF-16).Cause: the cut is
str.substring(0, length - 1)with no surrogate check, unlike the siblingabbreviate/truncatewhich already guard their cuts withsplitsSurrogatePair.Fix: reuse
splitsSurrogatePair(str, length - 1)to drop both halves when the final char is a low surrogate. The\r\nhandling and every documented example stay unchanged.mvn.