This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-11-03
Channels
- # announcements (55)
- # babashka (14)
- # beginners (49)
- # biff (9)
- # calva (73)
- # cider (14)
- # clerk (8)
- # clj-kondo (6)
- # clojure (92)
- # clojure-dev (4)
- # clojure-europe (18)
- # clojure-norway (62)
- # clojure-uk (5)
- # clojuredesign-podcast (4)
- # clojurescript (34)
- # cursive (40)
- # data-science (4)
- # datomic (5)
- # dev-tooling (1)
- # eastwood (6)
- # emacs (107)
- # figwheel-main (9)
- # fulcro (13)
- # gratitude (9)
- # hyperfiddle (5)
- # introduce-yourself (2)
- # off-topic (45)
- # overtone (23)
- # portal (5)
- # releases (3)
- # shadow-cljs (6)
- # specter (1)
- # squint (32)
- # timbre (4)
- # vscode (2)
Interesting today I noticed that I get objects in the js logs from timbre while I would normally have some clojurescript could it be a change due to this commit? https://github.com/taoensso/timbre/commit/0c5e07e709a1a785a87c97c9a13c9a564e3f1d12
I can confirm that after going back to 3.1.0 I get:
INFO [brian.ui-components.courses.current-course:64] - :loading-content-header [:course/id 13]
again,
while with the latest version of Timbre it's something likeINFO [brian.ui-components.courses.current-course:64] - Object Object
Hi Eric, apologies for the delay replying - I rarely have the opportunity to get on Slack. Would you please create an https://github.com/taoensso/timbre/issues on Timbre's GitHub page?
Unless you're enabling the :raw-console?
option (as described in the linked appender's docstring), there's no immediately obvious reason why you'd be seeing this changed behaviour.
If you do create an issue, please try provide as much context as possible - incl. what version of Timbre you're using, what it is you're actually logging, and if you're using any middleware.
Thanks!