Introduce support for multiple logging providers.

[fr33r]

Description

Up to this point, we only supported using zap as the logging package. These changes add support for the following packages:

• log
• log/slog
• logrus

Additionally, the unit.WithLogger option allows for supporting arbitrary custom loggers that support the unit.Logger interface.

NOTE: Since log/slog was introduced in 1.21, these changes also update CI to only support 1.21, 1.22, and 1.23 for V4.

Rationale

Supporting only zap imposes this package on clients of this package if they desire to having logging enabled. There are many logging solutions available, so only supporting a single package limiting.

Suggested Version

v4.0.0-beta.7

Example Usage

// use a *log.Logger.
opt := unit.WithStandardLogger(log.Default())

// use a *slog.Logger.
opt = unit.WithStructuredLogger(slog.Default())

// use a *logrus.Logger.
opt = unit.WithLogrusLogger(logrus.StandardLogger())

// use a custom logger satisfying unit.Logger interface.
opt = unit.WithLogger(&adapters.NewLogrusLogger(logrus.StandardLogger()))

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 99.35%. Comparing base (9687196) to head (cf47207).
Report is 4 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master     #135      +/-   ##
==========================================
+ Coverage   98.72%   99.35%   +0.63%     
==========================================
  Files          14       14              
  Lines        1407     1391      -16     
==========================================
- Hits         1389     1382       -7     
+ Misses         14        7       -7     
+ Partials        4        2       -2     

Flag	Coverage Δ
v3	98.71% <ø> (ø)
v4	99.86% <100.00%> (+1.14%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.