-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
unused doesn't work with "exported-is-used" and "exported-fields-are-used" linter settings #4218
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
Comments
Hey, thank you for opening your first Issue ! 🙂 If you would like to contribute we have a guide for contributors. |
Hello, sadly we cannot filter the elements that produce the panic because it's related to unexported fields, so I think we will remove the options |
That’s a shame… I would love to properly detect dead code in a rather large repository with no external dependents, so exported types should be imported elsewhere. Nevertheless, if it’s not feasible to fix this, I’ll have to search further |
I've been able to use |
Looks like problem in dependency (honnef.co/go/tools). It looks like it was not ready for some values. I enabled ![]() ![]() |
Also see dominikh/go-tools#1474 and dominikh/go-tools#1385. |
This comment was marked as off-topic.
This comment was marked as off-topic.
Also ran into this issue. This is the setting that I was most looking forward to 😢. Seems like there hasn't been any movement here? |
Tooday I start to use There is my command
|
Welcome
Description of the problem
When using unused with either "exported-is-used" or "exported-fields-are-used" linter settings or both, golangci-lint panics.
I have both tried in go 1.20 and 1.21
Version of golangci-lint
Configuration
Go environment
Verbose output of running
A minimal reproducible example or link to a public repository
https://github.com/pietdevries94/golangci-lint-unused-reproduction
Validation
The text was updated successfully, but these errors were encountered: