Issue #254: support exclamation point as ending char in path #255
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
|
|
|
@kaushlakers can you take a look? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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 addresses the issue in 'extractUrlsWithIndices' function where it does not properly recognize the full URL if the ending character in the path is an exclamation point (!). With a URL as such:
https://www.domain.com/locale/#!?key1=value1&key2=value2
The complete URL 'https://www.domain.com/locale/#!?key1=value1&key2=value2' will be recognized as a URL instead of just the part preceding the exclamation point 'https://www.domain.com/locale/#'.