-
-
Notifications
You must be signed in to change notification settings - Fork 267
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
Not clear in documentation how pathblacklist works #23
Comments
Open and closed instantly. Its a good point though. I think that the blacklist should not apply out of the root. Any reason for closing this so quickly? I think its a good thing to include. |
I also can't figure out how to blacklist nested vendor directories. This is important for a go directory containing many packages with their own vendor directories. |
Odd @montanaflynn because if you say do the following running against
It will exclude the root vendor directory, and as such not even walk what is inside it. Hence any nested ones will also be missed. I am suspecting perhaps this is not the behavior you are expecting? Could you supply a |
I was referring to nested vendor directories @boyter, here's a tree:
I want to count |
Ah fair point. The blacklist is literally just based on the root. I should probably add a new option that allows nested folders to be excluded. |
@boyter in modern javascript/typescript land it is very common to include |
Currently there is none. I am thinking perhaps a regex exclusion that you can use to exclude matching folders or files might be the best approach to take here. It would allow deprecation of the |
Sitting on the branch,
|
@montanaflynn @mcanfield I belive that the above would solve the issue for you. Let me know if you disagree and we can revisit this. |
@boyter thanks, I verified it would solve the issue for me.
One thing I might change is listing the relative directory path in the verbose logging so you don't see just the last exluded directory name like:
|
@boyter Heya, yup I just gave it a try and the regex filter works great! 🎉 This tool has now become a favorite :). Thank you much! |
@mcanfield Great to hear that. Slight tweak to include the full path as suggested by @montanaflynn
|
Going to close this on the basis both @mcanfield and @montanaflynn indicate that this resolves their issues. |
scc/processor/file.go
Line 87 in 012df08
No mention I noticed from the example that it includes the root, and not clear why you might want to potentially blacklist files outside the root?
The text was updated successfully, but these errors were encountered: