This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2024-05-28
Channels
- # announcements (19)
- # aws (4)
- # babashka (17)
- # beginners (74)
- # biff (2)
- # calva (5)
- # cider (6)
- # clerk (14)
- # clj-kondo (12)
- # cljs-dev (3)
- # clojure (40)
- # clojure-dev (26)
- # clojure-europe (28)
- # clojure-nl (1)
- # clojure-norway (39)
- # clojure-sweden (1)
- # clojure-uk (4)
- # conjure (2)
- # docker (35)
- # emacs (24)
- # graalvm (15)
- # graphql (1)
- # gratitude (4)
- # holy-lambda (2)
- # hyperfiddle (8)
- # introduce-yourself (3)
- # jobs (3)
- # nrepl (2)
- # off-topic (9)
- # pedestal (8)
- # reitit (5)
- # releases (3)
- # remote-jobs (3)
- # yamlscript (1)
how can I configure the "Refresh Changed Namespaces" command? I see that there is a refresh
helper function: https://github.com/BetterThanTomorrow/calva/blob/4dcc69a00393566ec72b7d7ebb935b52960e9d20/src/nrepl/index.ts#L819
How can I pass arguments? I'd like to execute a custom clojure function after the refresh
Unfortunately those arguments are not being exposed to the command: https://github.com/BetterThanTomorrow/calva/blob/dev/src/refresh.ts
And we’re not even returning the promise correctly so you can’t reliably string the command together with runCommands
…. Issue welcome.
I created this issue: https://github.com/BetterThanTomorrow/calva/issues/2556
In the mean time, as a work around, does Calva exposes the nrepl client? I'm wondering if I could send the refresh
(https://docs.cider.mx/cider-nrepl/nrepl-api/ops.html#refresh) operation directly to the nrepl client from Calva
@U0ETXRFEW thanks for the info