Handle unicode characters on TrimStrings middleware #40596
Closed
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
* 10.x-dev * version * Update splitter * Prepare Laravel 10 components * Bump testbench
# Conflicts: # CHANGELOG.md
|
sending to 9.x |
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.
PR #38117 introduced the ability to other space unicode characters to the
TrimStringsmiddleware.As issue #40577 stated the current implementation conflicts with some other unicode characters which end with the same escape sequence as the NBSP character.
In particular these japanese characters:
E381A0)E383A0)The implementation from PR #38117 causes the
A0sequence to be trimmed, which converts the sequence to an invalid one.This PR:
preg_replaceto trim the spaces using the proper modifiersCloses #40577