-
-
Notifications
You must be signed in to change notification settings - Fork 64
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
ignorepattern not working? #34
Comments
Oops, my bad, I simply forgot to take in account this option 😊 I added a test method, but please can you confirm it works for your case ? |
I tried it out, and it's working now! Thank you! 🌟 |
Hi Sorry to reopen, but it seems to be not working on macos? :
And results contain:
|
Did you try npm-groovy-lint --files '**/*.groovy' --ignorepattern
'/bin/**/*' ? :)
Please can you send the full log ?
Le jeu. 21 mai 2020 à 15:41, Tomáš Hartmann <notifications@github.com> a
écrit :
… Hi Sorry to reopen, but it seems to be not working on macos? :
npm-groovy-lint --files '**/*.groovy' --ignorepattern 'bin/**/*'
And results contain:
/Users/i337562/devel/fiori.pipeline/bin/target/test-classes/vars/blabla.groovy
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<#34 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AEFQSDTGGCIPH2ZJVZESNY3RSUVPTANCNFSM4MUZ2E3Q>
.
|
I tried, still the same, full log you mean with some verbose settings? |
|
Please can you try the following command and post the full log ? (in private to nicolas.vuillamy@gmail.com if you don't want your log details to be posted publicly :) ) |
I think it would work with |
as discussed by mail, problem solved with |
I'm trying to use the
--ignorepattern
option on the command line, but it doesn't seem to be working as expected. Specifically, I would like to ignore the usualnode_modules
directory.I've tried several variations on the pattern with no luck. Is this a bug, or am I just missing the right format?
I'm currently running on Windows 10 with:
The text was updated successfully, but these errors were encountered: