would that work with calva? or cursive?

(never wrote CIDER middleware, so clueless here)

you talk about REPL session. I think it's more natural to inject something in that REPL session than into static analyzer tools

since REPL = runtime

perhaps throwing an exception with some stacktrace will do the right thing automatically

you could do trick using clj-kondo hooks where the hook generates errors

and you refresh the hook at runtime

and then clj-kondo will report it on the next lint (not sure in the case of clojure-lsp, it should refresh the config if one of the hook code has changed, which it should do anyway)

:thinking_face: the flow is: 1. you call mallli.dev/start! in repl 2. you define function schemas 3. dev-toolong listens to registry changes and runs tests for that -> know if it's not right (var + error) 4. now, just prints that

ok in the case of 4, I think throwing an exception would probably be what triggers CIDER to render the error in the code

or whatever other tool, like socket REPL tooling

thanks, need to test. The checking is done in background on var watcher, so not sure where the exception would end up.

Sometimes people have setup an uncaught exception handler which makes it log somewhere

With the right deps.edn alias Calva should support custom nrepl middleware, I think.

https://nixpk.gs/pr-tracker.html?pr=130038

thx!

Thanks!