This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-03-01
Channels
- # announcements (7)
- # babashka (10)
- # beginners (60)
- # clerk (4)
- # clojure (19)
- # clojure-conj (5)
- # clojure-europe (48)
- # clojure-nl (1)
- # clojure-norway (6)
- # clojure-uk (2)
- # clojurescript (12)
- # conjure (2)
- # core-async (24)
- # cursive (3)
- # datalevin (18)
- # events (1)
- # figwheel-main (5)
- # fulcro (22)
- # honeysql (29)
- # hyperfiddle (60)
- # jobs (3)
- # leiningen (18)
- # lsp (47)
- # meander (21)
- # missionary (6)
- # off-topic (35)
- # reagent (14)
- # remote-jobs (1)
- # ring (1)
- # shadow-cljs (32)
- # sql (10)
- # transit (12)
Greetings! Would it be possible to expose babashka.impl.nrepl-server/start-server!
? Then I could add a task like aws-nrepl {:task (babashka.exposed-or-whatever.nrepl-server/start-server!)}
which has all the :requires
loaded and ready to go? Thoughts?
... as well as the ability to have run initialisation/connection code 🙂
if i understand this correctly shouldnt the public ns babashka.nrepl.server
do the same thing?
Oh, it is public? I obviously didn't do a good search
I searched docs for nrepl-server
and then did a github search but came across the wrong code obviously.
yep, in the https://book.babashka.org/, look for The babashka.nrepl.server API is exposed since version 0.8.157.
Ah, you won't find it if you search for nrepl-server
. Thwarted by a dash.