staticcheck: Add option for passing folders that should be avoided

[Jacalz]

It would be great if you could pass a folder (or folders) where you don't want staticcheck to check the .go files. Useful if you, for example, are vendoing a different go module outside of the normal vendor folder.

[Jacalz]

Might be related to #429

[ainar-g]

That's a relatively simple POSIX Shell script though:

$ go list ./... | grep -F -e example.com/bad/pkg -v | xargs staticcheck

[Jacalz]

Thanks @ainar-g. That is quite a good workaround until this is solved in a better way :)
Preferably, having this as an option in something like staticcheck.conf.

[dominikh]

until this is solved in a better way
There will likely not be a better way. Passing the packages you want checked on the command-line is exactly the way to solve this. If the ... pattern matches too many packages, then you'll have to use something like Ainar's approach to filter that list. This is in line with tools like go test, where go test ./... will (probably?) also run more tests than you intended.

You could also place a staticcheck.conf at the top of your "vendor" directory that disables all checks (checks = []) – but you may have to delete nested staticcheck.conf files if your vendored dependencies have any, or they might re-enable checks.