This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-11-24
Channels
- # adventofcode (4)
- # announcements (1)
- # aws (6)
- # babashka (18)
- # babashka-sci-dev (18)
- # beginners (12)
- # calva (43)
- # circleci (3)
- # clj-kondo (96)
- # cljdoc (2)
- # clojure (89)
- # clojure-australia (2)
- # clojure-europe (26)
- # clojure-nl (3)
- # clojure-norway (11)
- # clojure-spec (8)
- # clojure-uk (1)
- # clojurescript (28)
- # cursive (25)
- # datahike (6)
- # datalevin (56)
- # datomic (12)
- # docker (15)
- # emacs (9)
- # events (2)
- # figwheel (3)
- # fulcro (15)
- # gratitude (10)
- # introduce-yourself (8)
- # lsp (16)
- # malli (6)
- # nbb (2)
- # off-topic (23)
- # other-languages (2)
- # pathom (4)
- # portal (25)
- # practicalli (1)
- # re-frame (9)
- # releases (1)
- # shadow-cljs (8)
- # sql (6)
- # timbre (3)
> Would strongly recommend against using > Timbre through tools.logging unless you absolutely must I just noticed https://github.com/ptaoussanis/timbre/blob/226ffa11e2f9293a274dd8a7147e20add5a040fa/src/taoensso/timbre/tools/logging.clj#L5 Until today, I thought that abstracting logging implementations via clojure.tools.logging was a good practice, especially for libraries, otherwise everything that consumes it downstream is forced to have timbre -or whatever implementation the library uses- as a dependency as well. This can also be an issue if for instance you want to set up a custom appender (e.g. JSON) and you're using a different logger implementation in your artifact, in which case you have to configure the appender at least twice. So I guess my question is what are some practical reasons not to use clojure.tools.logging with timbre?
I see, should have seen that the first time 😞 Thanks, could be a potential problem because we need some of that information but I'll see what I can do.