revive
wrapcheck
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
revive
-
revive v1.3.4 is now available
The v1.3.4 of revive, the fast, configurable, extensible, flexible, and beautiful linter for Go, is available.
-
net/http extension to exchange structs
I would suggest checking out something like revive to improve the code. For instance you use an errors.New(fmt.Sprintf(... when you can just use fmt.Errorf(... to simplify it. I am not saying obey everything but there are some good lints included that can even catch bugs (for instance misusing errors.Is or errors.As or general equality).
-
Why elixir over Golang
Linting and static analysis: https://revive.run/
- Just migrated our Open Source project to Golang
-
Revive 1.3 is out
For people using this linter (like me) https://github.com/mgechev/revive
-
Is there a better alternative to `gofmt`?
Been using https://github.com/mgechev/revive in all my projects.
-
Change Blogging my first Hacktoberfest (2021)
The day after, I talked about the Hacktoberfest to Salvador (architect colleague and my technical/career unofficial mentor). He is known for contributing to revive a Golang linter. We decided that I could contribute by solving these 3 issues (2 new rules and add a docker image to the release). Since this moment, I have been coding every available hour I had. It felt so reviving to spend time coding on new projects, rewarding to solve issues for people actually using the tool. Here are all my contributions.
-
Golang Style Checkers
While golint may be deprecated it has been brought back as revive. You can also enable in golangci-lint.
- Mgechev/revive: faster,stricter,configurable,extensible,replacement for golint
-
pre-commit-golang v0.8.3 - Now with revive support
This release adds support for revive, a ~6x faster, stricter, configurable, extensible, and beautiful drop-in replacement for golint.
wrapcheck
-
Structured Logging with Slog
This is such an infuriating problem. I'm convinced I'm using Go wrong, because I simply can't understand how this doesn't make it a toy language. Why the $expletive am I wasting 20-30 and more minutes per week of my life looking for the source of an error!?
Have you seen https://github.com/tomarrell/wrapcheck? It's a linter than does a fairly good job of warning when an error originates from an external package but hasn't been wrapped in your codebase to make it unique or stacktraced. It comes with https://github.com/golangci/golangci-lint and can even be made part of your in-editor LSP diagnostics.
But still, it's not perfect. And so I remain convinced that I'm misunderstanding something fundamental about the language because not being able to consistently find the source of an error is such an egregious failing for a programming language.
-
Wrapcheck v2.3.0 released: Ignore package signatures
If you're curious to read more, you can have a read here: https://blog.tomarrell.com/post/introducing_wrapcheck_linter_for_go
What are some alternatives?
go-critic - The most opinionated Go source code linter for code audit.
emperror - The Emperor takes care of all errors personally
go-tools - Staticcheck - The advanced Go linter
dockle - Container Image Linter for Security, Helping build the Best-Practice Docker Image, Easy to start
emusak-ui - This is a tool which allows you to download saves or mods for Nintendo Switch emulators using a compatible Emusak backend
ALVR - Stream VR games from your PC to your headset via Wi-Fi
errcheck - errcheck checks that you checked errors.
ireturn - Accept Interfaces, Return Concrete Types
json-log-explorer - UI for exploring JSON logs
gofumpt - A stricter gofmt
chock - Golang Result handling package