Fork me on GitHub
#shadow-cljs
<
2024-01-10
>
mauricio.szabo05:01:46

Hi, @thheller, a question: does the shadow-cljs nREPL implementation implements the "completions" operation?

thheller08:01:32

no, cider does

mauricio.szabo14:01:16

Ok, so not even the simplified completions operation (this one: https://nrepl.org/nrepl/1.1/ops.html#completions) right? Just to be sure, I'm implementing some stuff in my tooling and I'm confirming if it's not a bug on my side 🙂

thheller15:01:19

this has never existed for CLJS no

mauricio.szabo15:01:47

Oh, I meant for nREPL in CLJ - when I connect to nREPL in Shadow, I first land in clojure-land, and even there there's no "completions" operation right?

thheller15:01:51

no clue tbh. thats the default nrepl server, no clue what it has by default

mauricio.szabo15:01:24

Oh, that's weird... ok, thanks, I'll try to figure out what's happening.

thheller15:01:02

could be that its controlled by the middleware which I maybe didn't add?

thheller15:01:22

been a while since I looked at nrepl 😛

mauricio.szabo15:01:18

(For context - I was doing some testing on my plug-in and was connecting to the shadow-cljs nREPL server to run the tests, and that's how I found that trying to run completions got me an error)

mauricio.szabo16:01:31

Just a last question: is it possible to dynamically add this middleware/operation? Maybe with some config, maybe some API?

thheller16:01:10

:nrepl {:middleware [that.symbol]} in shadow-cljs.edn

thheller16:01:12

dynamically no

thheller16:01:31

(at least not that I know of, that would be an nrepl question)