Fix handling of a URL which has a non-hash componenet in the place of a hash#37
Merged
XhmikosR merged 3 commits intoAug 30, 2019
Conversation
XhmikosR
reviewed
Aug 30, 2019
XhmikosR
reviewed
Aug 30, 2019
Collaborator
|
@rakeshpai: LGTY? |
Member
|
LGTM 👍 |
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
3 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.
In the event a URL contains a 7 or 32-character segment where there would normally be a hash and exception would be raised:
TypeError: Cannot read property '0' of null at Object.stripVersion (<omitted>/frontend/node_modules/staticify/index.js:90:61)This PR fixes this by handling the possibility that the RegEx check would fail by completing a null check.