Improved support for numeric brace ranges #170
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.
Description
This PR improves support for numeric brace ranges in micromatch globbing ( ie
{1..9}
). The top-level methodsmicromatch
,isMatch
,makeRe
andcapture
are modified to use the newly introducedbraces
module. New test cases have been introduced to cover these additions.This PR also introduces some disabled test cases which cover errors in the upstream braces module, specifically bugs with conversion of zero-padded brace range to regex ( ie
{000...200}
).Since this functionality is already covered in docs, no changes have been made to README. Version has been bumped to 4.0.3, reflecting a patching of existing functionality.