Fixing URL shortening for URLs with Arabic characters. #1651
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.
Description
When URLs have unescaped Arabic characters, they are not extracted correctly. This happens not only with the library we use (
twitter-text
), but also with Ruby'suri
library andpostrank-uri
gem:So, the fix here is to first escape URLs that contain Arabic characters before sending them to the URL extraction method when shortening URLs.
Fixes CV2-3690.
How has this been tested?
TDD. I added a unit test that reproduced the issue.
Things to pay attention to during code review
Resources, reports and newsletters are affected by this change. The fix should just be applied for input texts with Arabic characters.
Checklist