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
"pattern" takes precedence over "ignore" #604
Comments
thank you, will take a look |
Any chance there might be traction on this in the future? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
If
pattern
is specified and has overlap withignore
, thenignore
doesn't work properly.To Reproduce
Config file:
Then run
npx jspcd
If I rename my config file and run
npx jscpd --ignore "**/node_modules/**/*,**/.next/**/*"
, then it behaves as expectedSimilarly,
npx jscpd --pattern "./reactCommon/**/*" --ignore "**/node_modules/**/*,**/.next/**/*"
triggers the problemExpected behavior
the
./reactCommon/.next
folder should be ignoredActual behavior
I get a lot of dupe warnings for lines in the
./reactCommon/.next
folderScreenshots
Desktop (please complete the following information):
Additional context
Note that the same behavior seems to occur no matter how I format the ignore line (i.e. use a full relative path, omit ** or *, etc) or whether I use a string or array of strings
The text was updated successfully, but these errors were encountered: