This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-11-04
Channels
- # announcements (30)
- # aws (7)
- # babashka (7)
- # beginners (64)
- # calva (39)
- # cherry (17)
- # cider (1)
- # clj-on-windows (6)
- # clojure (30)
- # clojure-austin (12)
- # clojure-europe (25)
- # clojure-nl (2)
- # clojure-norway (23)
- # clojure-spec (23)
- # clojure-uk (6)
- # clojurescript (20)
- # cursive (18)
- # datahike (3)
- # datalevin (12)
- # datomic (9)
- # etaoin (5)
- # graalvm (45)
- # instaparse (2)
- # interceptors (11)
- # kaocha (1)
- # lsp (102)
- # meander (6)
- # nbb (16)
- # off-topic (30)
- # pathom (83)
- # pedestal (6)
- # portal (5)
- # re-frame (12)
- # reitit (5)
- # rewrite-clj (10)
- # scittle (35)
- # shadow-cljs (49)
- # spacemacs (10)
- # vim (14)
If I am trying to tap an exception into Portal, is calling Throwable->map
on that exception first redundant?
I guess it depends on what you want. By tapping the exception directly, you have access to the original exception type. Also, the exception type will be pr-str'd and the value will try to be interpreted as edn by the Portal UI which is similar to the data that Throwable->map will produce.
There's a slight difference in display -- since Portal seems to recognize a hash map created from an exception via Throwable->map
-- but I find tap>
'ing exceptions directly works just fine for my needs.
Hah, yeah, what he said 🙂
Great, thanks @U1G869VNV @U04V70XH6. I just started with Portal this morning and it is so cool!
