This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-04-24
Channels
- # announcements (4)
- # babashka (75)
- # beginners (57)
- # calva (26)
- # cider (1)
- # clj-kondo (18)
- # cljs-dev (2)
- # clojure (31)
- # clojure-czech (1)
- # clojure-europe (23)
- # clojure-france (3)
- # clojure-germany (2)
- # clojure-uk (3)
- # clojurescript (23)
- # conjure (9)
- # data-oriented-programming (5)
- # datomic (14)
- # defnpodcast (1)
- # deps-new (12)
- # expound (4)
- # fulcro (32)
- # helix (4)
- # jackdaw (70)
- # joker (1)
- # malli (1)
- # music (2)
- # off-topic (19)
- # other-languages (6)
- # podcasts-discuss (5)
- # portal (6)
- # quil (5)
- # re-frame (16)
- # shadow-cljs (14)
- # spacemacs (7)
- # vim (5)
- # xtdb (22)
How would i configure it so i get expound wrapped spec error messages in the "cider-error" buffer rather then the default ones?
My understanding (and I’m not a cider expert, so take this with a grain of salt), is that it would require changes to the cider error buffer and/or the nREPL error handler. When an error is returned from nNEPL, cider seems to check if it’s a spec error and then formats it in a custom way. There would need to be a way to send the error to expound for formatting.
Or maybe, more accurately, nREPL would need to adjust the error message before it sends it to cider. I think this is how the Clem middleware works https://gitlab.com/unc-app-lab/clem
@drewverlee I’d certainly accept a PR for some nREPL middleware in the expound repo (assuming that it didn’t introduce any dependencies into Expound for non-cider users)