-
-
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: rules's severity config has no effect #3111
Labels
Comments
Hey, thank you for opening your first Issue ! 🙂 If you would like to contribute we have a guide for contributors. |
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
Is this being worked on? |
This comment was marked as off-topic.
This comment was marked as off-topic.
Fixed by #4452 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Welcome
Description of the problem
I tried to configure specific severity for some revive's rules but they are completely ignored.
I tried with revive directly and it works perfectly with this config file:
Version of golangci-lint
Configuration file
Go environment
Verbose output of running
Additionally, there is severity informations parsed with jq:
var-naming
andexported
should be at warning level according to my configuration file...Code example or link to a public repository
With my config it should return:
Which is not the intended result since the
var-naming
rule appear as error and not warningThe text was updated successfully, but these errors were encountered: