Adds support for regex flags #275
Open
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
This change adds support for regex flags. Currently if we want to supply flags such as i for ignore case, we must either pass in the RegExp object /\w+/i or pass it in as a flag parameter. Since we return the regex as a string, we cannot pass the Regex object via getInput. Instead this change proposes passing in flags as a separate input.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This change adds support for regex flags. Currently if we want to supply flags such as
ifor ignore case, we must either pass in the RegExp object/\w+/ior pass it in as a flag parameter. Since we return the regex as a string here, we cannot pass the Regex object viagetInput. Instead this change proposes passing in flags as a separate inputtitle-regex-flags.