-
Notifications
You must be signed in to change notification settings - Fork 20
Feature/linting #75
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
Feature/linting #75
Conversation
…-code-security-scanner
| log.Println("Failed opening file", path, err) | ||
| continue | ||
| } | ||
| defer file.Close() |
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.
the linting on these deferred file close calls is kind of annoying. I think in the dce repo I just did //nolint comments on them.
I might reconsider whether a failed file close is really a fatal error (line 64). I guess I'm not sure under what conditions that could happen (like if the file disappears?)
eschwartz
left a comment
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.
👍 👍 👍
Proposed changes
Enabled gofmtout and golangci-lint. Formatted code and fixed linting issues.
Merge #74 first.
Types of changes
Checklist
README.md, inline comments, etc.)CHANGELOG.mdunder a## nextrelease, with a short summary of my changesRelevant Links
Further comments