-
-
Notifications
You must be signed in to change notification settings - Fork 37
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix behavior for matching paths outside cwd #92
Fix behavior for matching paths outside cwd #92
Conversation
d9263cb
to
a799e79
Compare
Should be logic of detecting absolute/relative path go in minimatch instead? |
Sorry, seems I missed this one. |
Can you explain exactly what the breaking change is? What used to work and will no longer work (from a user's perspective)? |
I will return to PR in two weeks |
Bump |
Got stuck at minimatch.match('/A/B/C/d.js', '!/**/test.js') -> false
minimatch.match('/A/C/test.js', '!/A/B/**/*.js') -> false |
replace **/**/ to **/ in test
Got what, tried to exclude from empty set of files |
fix tests with ! only (not matches anything and whats good) fix behaviour checking test for !** test also comments
@sindresorhus described changes in test cases, most of them failing on old version |
Fixes #85 (not sure, maybe #87 too)
Here breaking changes:
Old behavior:
all paths, which is outside of current working directory, should be matched only by absolute path glob
New behavior:
you can match dirs outside current working dir
if you want match globally - start glob pattern with /
Removed test "should filter relative paths that leave current directory tree", because of breaking change
IssueHunt Summary
Referenced issues
This pull request has been submitted to:
IssueHunt has been backed by the following sponsors. Become a sponsor