active-group / active-logger Goto Github PK

We are using timbre v5.2.1 (master, redo-metrics)

in timbre v5.2.1

  (def example-config "DEPRECATED, prefer `default-config`" default-config)

We are using it (master, redo-metrics)

We're still using master as the default branch. It would be nice to use main to avoid the bad name and have symmetry with our other projects.

• Split up active-logger into
  • active-logger-api that uses the SLF4J facade as the "backend"
  • and active-logger-timbre that uses timbre-slf4j as the backend and wraps timbre-specific stuff like configuration as active-logger does now
• Tie both together in active-logger in such a way that it transparently provides the same functionality as it does now

active-logger is then useful for stand-alone applications as it is now, active-logger-api is then useful for libraries.