You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Go ecosystem has a lot of opinionated logger, slog is indeed the one proposed by the standard library, it is good for general-purpose application but may fall short for high-performance applications.
If you are okay with that, I may contribute to wRPC Go codebase by allowing users to pass custom Loggers using the API of https://github.com/go-logr/logr so they integrate better with:
The NATS Client wrapper,
The generated bindings,
WDYT?
The text was updated successfully, but these errors were encountered:
If so, perhaps we could introduce an interface mimicking slog API and a global logger variable in wRPC Go module with setters and getters, which would allow users to customize this?
That sounds like a really good idea indeed, and I also understand your concerns about expanding the dependencies.
Let's do our own custom interface so! Just we need to think about how we can make this interface support structured logging then..
I am pretty surprised the standard library doesn't have already an API.. that would have been really handy..
The Go ecosystem has a lot of opinionated logger,
slog
is indeed the one proposed by the standard library, it is good for general-purpose application but may fall short for high-performance applications.If you are okay with that, I may contribute to wRPC Go codebase by allowing users to pass custom Loggers using the API of https://github.com/go-logr/logr so they integrate better with:
WDYT?
The text was updated successfully, but these errors were encountered: