Add regexp capturing in rules #264
Open
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 PR allows regexp capturing and backreferencing to
task_patternin rules.Regexp.last_match($~) will be set inProcs at bothsourceandaction.last_matchrelated special variables, such as$1,$&,$`, and$', will also be set.sourceis aString, it may contain backreferences totask_patternby same format asString#sub.Here are some examples:
This can make
icon-32x32.pngfromicon.svg.This can make
build/index.html.enfromdoc/en/index.md.Although it passes all the tests, it will break backward compatibility in some cases:
Procs that refer toRegexp.last_matchrelated variables assigned outside the rule blockStringsources that include backslashes (directory separator in Windows?)Former case example:
Any feedback would be appreciated. Thanks.