-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
revive - exported rule does not work #2439
Comments
Hey, thank you for opening your first Issue ! 🙂 If you would like to contribute we have a guide for contributors. |
let me check this, it should be something with a update: it has nothing to do with a |
The isses are suppressed by default run:
concurrency: 4
timeout: 1m
linters-settings:
revive:
ignore-generated-header: true
severity: warning
rules:
- name: exported
arguments: [ "checkPrivateReceivers", "sayRepetitiveInsteadOfStutters" ]
linters:
disable-all: true
enable:
- revive
issues:
exclude-use-default: false |
thank you sooooooooooooooooooo much |
Thank you, @butuzov. You saved me from filing a bug. :) |
Ran into this myself, the workaround is to add two lines to .golangci-lint:
Why was this bug closed? This feels like a serious usability problem; it took me hours to figure out why this golint warning wasn't being emulated... it takes me about an hour to recover every time this warning does not fire. |
Because the answer is here: We have another issue to remove the excludes by default: #456 |
Thank you for linking to #456. |
Welcome
Description of the problem
Standalone revive usage gives:
$ revive ./... main.go:5:6: exported type Foo should have comment or be unexported
but
golangci-lint run -v
gives nothing:I tried every possible config options... Here is what use:
.golangci.yml
Version of golangci-lint
Configuration file
Go environment
Verbose output of running
Code example or link to a public repository
The text was updated successfully, but these errors were encountered: