You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The upgrade of errcheck in #1319 resulted in a regression where there is no option to use the .golangci.yml config file to skip the default errcheck excludes.
The default errcheck excludes are imported in this line:
From this point onward, golangci config file can only append to the Symbols slice, but not remove from it. The errcheck standalone tool has an option to skip these excludes with its flag errcheck --excludeonly, but the golangci tool does not have an equivalent.
Expectation: linters-settings.errcheck.* options from the golangci config file should include a way to skip the default errcheck excludes, allowing errcheck to report all violations found instead of just a subset of them.
Version of golangci-lint
$ golangci-lint --versiongolangci-lint has version v1.42.1 built from (unknown, mod sum: "h1:nC4WyrbdnNdohDVUoNKjy/4N4FTM1gCFaVeXecy6vzM=") on (unknown)
Welcome
Description of the problem
The upgrade of errcheck in #1319 resulted in a regression where there is no option to use the
.golangci.yml
config file to skip the default errcheck excludes.The default errcheck excludes are imported in this line:
golangci-lint/pkg/golinters/errcheck.go
Line 143 in 0e7233e
From this point onward, golangci config file can only append to the Symbols slice, but not remove from it. The errcheck standalone tool has an option to skip these excludes with its flag
errcheck --excludeonly
, but the golangci tool does not have an equivalent.Expectation:
linters-settings.errcheck.*
options from the golangci config file should include a way to skip the default errcheck excludes, allowing errcheck to report all violations found instead of just a subset of them.Version of golangci-lint
Configuration file
Go environment
Verbose output of running
Code example or link to a public repository
n/a
The text was updated successfully, but these errors were encountered: