This repository has been archived by the owner on Feb 15, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 1
golint reporting several "should have comment or be unexported" linting issues #92
Comments
I've opened an issue here since it appears the issue is with golangci-lint itself: See also atc0005/todo#29. |
atc0005
added a commit
that referenced
this issue
Jul 16, 2020
- Update Makefile to add separate, explicit golint command against all content *except* for vendored deps - this is until the golangci-lint tool can be fixed or whatever configuration setting that I am not applying can be tweak - Fix "exported const XYZ should have comment or be unexported" linting issues refs GH-92
atc0005
added a commit
that referenced
this issue
Jul 16, 2020
- Update Makefile to add separate, explicit golint command against all content *except* for vendored deps - this is until the golangci-lint tool can be fixed or whatever configuration setting that I am not applying can be tweaked - Fix "exported const XYZ should have comment or be unexported" linting issues refs GH-92
atc0005
added a commit
that referenced
this issue
Jul 16, 2020
- Update Makefile - add separate, explicit golint command against all content *except* for vendored deps - add installation step for golint - this is intended as a hotfix until the golangci-lint tool can be fixed or whatever configuration setting that I am not applying can be tweaked - Fix "exported const XYZ should have comment or be unexported" linting issues refs GH-92
atc0005
added a commit
that referenced
this issue
Jul 16, 2020
- Update Makefile - add separate, explicit golint command against all content *except* for vendored deps - add installation step for golint - this is intended as a hotfix until the golangci-lint tool can be fixed or whatever configuration setting that I am not applying can be tweaked - Fix "exported const XYZ should have comment or be unexported" linting issues refs GH-92
atc0005
added a commit
that referenced
this issue
Jul 22, 2020
- Remove golint call from Makefile - Remove `--exclude-use-default` CLI flag - Add explicit config settings to disable default exclusions This same config change will need to be pushed to all other repos where I am using this config set. Note to self: Docker container sooner than later perhaps? - refs #92 - refs atc0005/todo#29 - refs atc0005/todo#22
atc0005
added a commit
that referenced
this issue
Jul 22, 2020
- Remove golint call from Makefile - Remove `--exclude-use-default` CLI flag - Add explicit config settings to disable default exclusions This same config change will need to be pushed to all other repos where I am using this config set. Note to self: Docker container sooner than later perhaps? - refs #92 - refs atc0005/todo#29 - refs atc0005/todo#22
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
While testing the code in a VM today (where golangci-lint wasn't set as the default linter), one of the files I had open was flagged with linting failures. When I checked closer by running this command:
golint -set_exit_status $(go list -mod=vendor ./... | grep -v /vendor/)
this is what I got back:
EDIT: After fixing these, one additional issue was flagged:
The text was updated successfully, but these errors were encountered: