This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-07-27
Channels
- # announcements (12)
- # babashka (18)
- # bangalore-clj (3)
- # beginners (110)
- # calva (14)
- # cestmeetup (4)
- # cider (4)
- # clj-kondo (2)
- # clojure (34)
- # clojure-colombia (5)
- # clojure-europe (11)
- # clojure-nl (8)
- # clojure-spec (19)
- # clojure-uk (11)
- # clojurescript (16)
- # clojureverse-ops (8)
- # community-development (4)
- # conjure (65)
- # core-async (19)
- # cursive (22)
- # data-science (7)
- # datascript (1)
- # datomic (20)
- # devcards (1)
- # figwheel-main (64)
- # fulcro (10)
- # graalvm (3)
- # helix (3)
- # kaocha (22)
- # malli (68)
- # meander (6)
- # off-topic (39)
- # pathom (6)
- # pedestal (2)
- # reagent (5)
- # remote-jobs (2)
- # reveal (30)
- # rum (4)
- # shadow-cljs (83)
- # specter (3)
- # tools-deps (9)
- # xtdb (18)
I throw an ex-info with a spec-related explain-data (with ::s/failure) and my message is replaced. I think it's caused by this https://github.com/clojure-emacs/cider-nrepl/blob/7358676ae1db33b4807bfa1bbaa57879d54573ae/src/cider/nrepl/middleware/stacktrace.clj#L294
Is this a bug? I like the way the spec failure is printed, but I still would like to see my original error message with it.
can someone explain or point me to documentation on how CIDER assigns/links REPLs and editor sessions (.nrepl-port stuff?)
you probably saw it already, but just in https://docs.cider.mx/cider/usage/managing_connections.html