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
Currently we use our own Logging algebra, which allows us to test logging and abstract it away, however it's very unflexible.
It doesn't allow to disable logging for some classes at launch time
It doesn't show where logging is coming from
It doesn't allow to configure severity
log4cats gives us these abilities, but unfortunately has another downside - we need to either abandon F[_]: Logging signatures and instantiate one logger per class (and damage testing) or have Main class everywhere, which defeats 1st and 2nd points.
Currently we use our own
Logging
algebra, which allows us to test logging and abstract it away, however it's very unflexible.log4cats gives us these abilities, but unfortunately has another downside - we need to either abandon
F[_]: Logging
signatures and instantiate one logger per class (and damage testing) or haveMain
class everywhere, which defeats 1st and 2nd points.There's some WIP in log4cats I hope to get merged at some point (typelevel/log4cats#421, typelevel/log4cats#397). When the PR is merged we can migrate without trade-offs.
The text was updated successfully, but these errors were encountered: