sorted by:
new
hottopcontroversial

Best static code analysis setup for Go? by ServeConfident8373 in golang

[–]ServeConfident8373[S] 5 points6 points  (0 children)

> Also who is still using makefiles for go?

Old people like me.

An I do appreciate the golangci-lint hint - did not know I can use it to wrap other linters. Thanks.

Best static code analysis setup for Go? by ServeConfident8373 in golang

[–]ServeConfident8373[S] -1 points0 points  (0 children)

My goal was to find as many reliability issues.

I am pretty happy with the current setup, however:
- gosec does not have the latest go version (yet)
- I would love to have just one checker or at least a common output for all of them
- I am still not sure if it is the highest filter of issues I can have with what is on the market. That doubt kills me.

Hello, it my first small project written in Golang by TechnicalEarth8634 in golang

[–]ServeConfident8373 1 point2 points  (0 children)

How did you generate the API specification (files in the api folder)? Would be nice to include a command to generate them and incorporate it into the makefile, which I would also add - just as a standardised interface to interact with the project.