-
-
Notifications
You must be signed in to change notification settings - Fork 468
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
opts.ignore
not applied to results emitted by match
#194
Comments
+1 You can get around this today by doing something like: var glob = require('glob');
var isIgnored = require('glob/common').isIgnored;
var globber = new glob.Glob('**/*.js', {ignore: ['foo.js']});
globber.on('match', function onMatch(match) {
if (isIgnored(globber, match)) {
return;
}
// Do something will paths that are not ignored...
}); |
@mlmorg Unfortunately that's no help for my situation: using |
+1. I do
|
@mik01aj You should use |
Patch welcome for this. Probably just need to find the bits where |
Awesome, thanks! |
I've noticed that with this module, and a few others, about half the time I say "patch welcome" I end up just writing it later that afternoon... |
If only you could sense when you were going to say patch welcome a few weeks in advance... |
Thanks @isaacs. Sorry, I was going to take a look at it later tonight but glad you got to it first! |
Given glob@5.0.5, node v0.10.32, on linux, and the following test case:
I expect the output to be:
Actual output:
The text was updated successfully, but these errors were encountered: