-
Notifications
You must be signed in to change notification settings - Fork 820
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
Switch to golangci-lint #346
Switch to golangci-lint #346
Conversation
Build Succeeded 👏 Build Id: 9d7ee559-d2f4-4f95-ad9c-a20a3ef15ebc The following development artifacts have been built, and will exist for the next 30 days:
(experimental) To install this version:
|
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.
A couple of minor its, and a question.
But overall, this looks like this does a better job than gometalinter for linting, and locks it to a version AND runs faster. 👍 🏅
65cda51
to
db904c3
Compare
Build Succeeded 👏 Build Id: cf70a62d-23ed-4a57-aac2-c64ffad3b6a8 The following development artifacts have been built, and will exist for the next 30 days:
(experimental) To install this version:
|
I've made the switch to run golang-ci instead of gometalinter.
I've added all supported and not included by default linters of gometalinters and added:
Excluded files are now automatically handled, but examples/ was also skipped so I'm running the linter twice. See documentation examples below:
Found some interesting issues (typo and goimports) but also some false positives (dupl).
We should have this tools included in our IDE (there is vs-code support).
Closes #187
Closes #237