moq
zap
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.
moq
- vektra/mockery has fully released the "packages" feature! This blog explains what it is and how it works.
- Why elixir over Golang
-
Is gomock still maintained and recommended?
``` https://github.com/matryer/moq
-
How do you write/generate mocks for testing?
Currently trying out https://github.com/matryer/moq for the first time, and quite positive so far. Haven't pushed it enough yet to give a real opinion.
-
gomock giving me a hard time
I like moq much better than gomock. Much simpler and easier to work with.
-
how to mock DBs
Just replaced mockery generated mocks with https://github.com/matryer/moq Alot cleaner imo at least for me
- Testify Mocking conundrums
-
Can someone please comment on this mock example from Jon Calhoun's post on DDD?
btw, you can avoid making such mocks manually by using https://github.com/matryer/moq, which will generate such mocking code for you
-
How do you control behaviour in mocked interface ?
I like the way of matryer/moq a lot. Basically, it generates a func for each of the methods of an interface, therefore the behaviour is clear to everyone without too much abstraction.
-
What mocking framework do you prefer?
This one is easy to use, simple, powerful and idiomatic https://github.com/matryer/moq
zap
- Desvendando o package fmt do Go
-
Building RESTful API with Hexagonal Architecture in Go
The project currently uses slog package from standard library for logging. But switching to a more advanced logger like zap could offer more flexibility and features.
-
Structured Logging with Slog
It's nice to have this in the standard library, but it doesn't solve any existing pain points around structured log metadata and contexts. We use zap [0] and store a zap logger on the request context which allows different parts of the request pipeline to log with things like tenantid, traceId, and correlationId automatically appended. But getting a logger off the context is annoying, leads to inconsistent logging practices, and creates a logger dependency throughout most of our Go code.
[0] https://github.com/uber-go/zap
-
Kubebuilder Tips and Tricks
Kubebuilder, like much of the k8s ecosystem, utilizes zap for logging. Out of the box, the Kubebuilder zap configuration outputs a timestamp for each log, which gets formatted using scientific notation. This makes it difficult for me to read the time of an event just by glancing at it. Personally, I prefer ISO 8601, so let's change it!
-
Go 1.21 Released
What else would you expect from a structured logging package?
To me it absolutely makes sense as the default and standard for 99% of applications, and the API isn't much unlike something like Zap[0] (a popular Go structured logger).
The attributes aren't an "arbitrary" concept, they're a completely normal concept for structured loggers. Groups are maybe less standard, but reasonable nevertheless.
I'm not sure if you're aware that this is specifically a structured logging package. There already is a "simple" logging package[1] in the sodlib, and has been for ages, and isn't particularly fast either to my knowledge. If you want really fast you take a library (which would also make sure to optimize allocations heavily).
[0]: https://pkg.go.dev/go.uber.org/zap
[1]: https://pkg.go.dev/log
- Efficient logging in Go?
-
Why elixir over Golang
And finally for structured logging: https://github.com/uber-go/zap
-
Beginner-friendly API made with Go following hexagonal architecture.
For logging: I recommend using Uber Zap https://github.com/uber-go/zap It will log stack backtraces and makes it super easy to debug errors when deployed. I typically log in the business logic and not below. And log at the entry for failures to start the system. Maybe not necessary for this example, but it’s an essential piece of any API backend.
- slogx - slog package extensions and middlewares
- Why it is so weirdo??
What are some alternatives?
gomock - GoMock is a mocking framework for the Go programming language.
logrus - Structured, pluggable logging for Go.
mockery - A mock code autogenerator for Go
zerolog - Zero Allocation JSON Logger
Testify - A toolkit with common assertions and mocks that plays nicely with the standard library
slog
NSubstitute - A friendly substitute for .NET mocking libraries.
glog - Leveled execution logs for Go
counterfeiter - A tool for generating self-contained, type-safe test doubles in go
go-log - a golang log lib supports level and multi handlers
GORM - The fantastic ORM library for Golang, aims to be developer friendly
log - Structured logging package for Go.