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
Golang's logging ecosystem is vast, and users expect various logging models to be supported. For instance, one of our enterprise customers expects slog support. Currently, the package expects a Logger interface passed as means to log its events. Apparently this is not flexible enough.
Options to consider:
Remove logging altogether; return errors where appropriate.
Add explicit support for slog by adding a SetHandler method.
Simplify expected logger dependency by accepting a logFn function with one msg argument. Have a null logger as default.
The text was updated successfully, but these errors were encountered:
Golang's logging ecosystem is vast, and users expect various logging models to be supported. For instance, one of our enterprise customers expects
slog
support. Currently, the package expects aLogger
interface passed as means to log its events. Apparently this is not flexible enough.Options to consider:
slog
by adding aSetHandler
method.logFn
function with onemsg
argument. Have a null logger as default.The text was updated successfully, but these errors were encountered: