Closed nocturnalastro closed 1 week ago
I made a draft PR addressing the issues raised by running a default config of golangci-lint here: https://github.com/openshift/kube-compare/pull/23
+1, I have had good value from linting in the past. It's not a silver bullet for anything but I've seen had golangci-lint highlight genuine bugs, and improve runtime efficiency.
It spotted a shadowed definition which may have caused issues
Let's include the golangci-lint
yml config and call from our CI job as part of the PR
/kind feature
@pixelsoccupied @nocturnalastro can we close this?
Yes
Found some cases of errors not being handled or dropped. I suggest we add
golangci-lint
or some other linter as a blocker on merges to act as a guard against such things happening.