This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-10-05
Channels
- # beginners (46)
- # calva (89)
- # cider (24)
- # clara (7)
- # clj-kondo (36)
- # clojure (33)
- # clojure-australia (4)
- # clojure-dev (9)
- # clojure-europe (15)
- # clojure-israel (1)
- # clojure-nl (1)
- # clojure-uk (13)
- # clojurescript (55)
- # community-development (38)
- # conjure (1)
- # cryogen (12)
- # cursive (16)
- # data-science (4)
- # datomic (34)
- # events (2)
- # fulcro (5)
- # gorilla (3)
- # introduce-yourself (3)
- # jobs (9)
- # kaocha (5)
- # malli (16)
- # music (12)
- # off-topic (11)
- # polylith (4)
- # react (4)
- # reactive (1)
- # reagent (18)
- # remote-jobs (2)
- # reveal (2)
- # sci (4)
- # shadow-cljs (31)
- # timbre (4)
- # tools-build (70)
- # tools-deps (11)
- # vim (33)
- # xtdb (53)
morning
Morning
Has anyone here developed nREPL middleware? I'm having a go at it and I think I'm hitting some sort of caching issue where it refuses to pick up my changes.
I’ve done some pretty trivial ones; the most notable being nrebl.middleware. I don’t recall anything particularly unusual with it, you might want to check and make sure you’re passing vars not functions to set-descriptor
Thanks, that's a good thought, but it's not that...
How are you developing it? nREPL is slightly unusual if you’re using nREPL to develop nREPL. I’m assuming you’re using the recommended interactive hacking workflow? https://nrepl.org/nrepl/0.8/hacking_on_nrepl.html#interactive-hacking
I have recently started doing it like that - and it seems to be better.
Previously I was setting the middleware with the nrepl.edn file and then starting an nrepl from cursive. It works the first time and then seems to get cached and I can't seem to make it pick up my code sensibly.
I liked that approach because that was how I imagined using the middleware from other projects, so it seemed like a good test.