This repository was archived by the owner on Mar 15, 2018. It is now read-only.
Added ability to use regex in search#9
Open
legacybass wants to merge 1 commit intosongkick:masterfrom
legacybass:master
Open
Added ability to use regex in search#9legacybass wants to merge 1 commit intosongkick:masterfrom legacybass:master
legacybass wants to merge 1 commit intosongkick:masterfrom
legacybass:master
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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
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.
Added the ability to use RegEx with the search. In order to allow them and still use the JSON file, I introduced the concept of prepending the string with a ~~. This indicates the string should be treated as a RegEx. Use the standard JS RegEx literal format for the rest. You'll need to double escape any escape characters because it's inside a string, however.