Apply a stricter regex when scanning DeepLinkRegistry#30
Merged
felipecsl merged 1 commit intoairbnb:masterfrom Jul 17, 2015
Merged
Apply a stricter regex when scanning DeepLinkRegistry#30felipecsl merged 1 commit intoairbnb:masterfrom
felipecsl merged 1 commit intoairbnb:masterfrom
Conversation
Collaborator
|
thank you! |
felipecsl
added a commit
that referenced
this pull request
Jul 17, 2015
Apply a stricter regex when scanning DeepLinkRegistry
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
2 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.
Right now, the regex scheme set up in DeepLinkEntry allows for DeepLinkRegistry.parseUri to return early if there's a subset scheme already registered.
IE:
Appending the
$at the end of the regex should ensure that the whole String matches, rather than just the beginning.