-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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 fixes - part 3 #8872
Revive fixes - part 3 #8872
Conversation
[rule.var-naming]
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🤝 ✅ CLA has been signed. Thank you!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice. Please double check the struct elements exposed to toml
but not carrying an annotation as these might change the config option...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me, but might have missed some toml
issues... :-)
!retry-checks |
!retry-failed |
* * Revive fixes regarding following set of rules: [rule.var-naming]
Revive is fast, configurable, extensible, flexible, and beautiful linter for Go. Drop-in replacement of golint.
This is part3 of fixes for problems found for following set of rules:
don't use an underscore in package name
issues were not fixed -> Telegraf allows to have underscores in package names. This approach should be rethought or having underscores in packages should be ignored.