Enforce no golangci-lint warnings in CI#313
Conversation
|
It can use all golint warnings + quite a few others. Most importantly for CI purposes, the warnings can be silenced (and sometimes it's necessary for backward compatibility). |
d706935 to
c97adc7
Compare
4e7c65a to
80afc66
Compare
|
Of course the warnings will need to be fixed (or silenced) before merging this. |
|
Unfortunately this change requires bumping the supported version of Go to 1.11. This is actually not that bad, since that's the oldest version officially supported by the Go project since Feb 2019. |
|
@sbarzowski I think this can be easily merged now that minimum go version is 1.11 |
80afc66 to
364c761
Compare
d713e54 to
2e5a654
Compare
| for _, l := range lines { | ||
| if l[0] == '*' { | ||
| l = " " + l | ||
| for i := range lines { |
There was a problem hiding this comment.
@sparkprime I don't really understand the point of this. Why do we need this "little hack"?
FYI before my change this whole loop was a noop, because l was a copy.
|
|
||
| data.Sort() | ||
| err = data.Sort() | ||
| if err != nil { |
There was a problem hiding this comment.
This is probably the most consequential part of this change. In particular one of our tests already covers this, but I have missed it before (it was committed with a bad golden).
2e5a654 to
8dfb921
Compare
Some of the suggestions are minor bug fixes (missing error handling).
8dfb921 to
da35d37
Compare
No description provided.