-
Notifications
You must be signed in to change notification settings - Fork 50
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
Formatter, Linter and fixes #62
Conversation
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 useful PR. Thanks for submitting! Added some comments.
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.
LGTM, but unsure about the RequestHeaderTimeout.
.golangci.yaml
Outdated
|
||
linters: | ||
disable-all: true | ||
enable: |
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.
I would prefer to take a minimal approach to linting here. IMO too many linters leads to an annoying development experience and excessive comments to appease all of the linters. Can we stick to the official go toolchain?
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.
If there is a tool that should absolutely be added in excess of the standard toolchain, can we add a comment as to why it is needed and is not redundant?
I have removed the linter config and integration to move this forward. Personally, I have seen a lot of benefits in linters in addition to the Go toolchain but I am definitively not dogmatic about it. 👍 |
Closing old pull requests that are now conflicting after major refactor. |
See #49
Fixes issues found by a gosec run