This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # announcements (10)
- # beginners (53)
- # calva (22)
- # clj-kondo (21)
- # cljs-dev (1)
- # clojure (18)
- # clojure-europe (2)
- # clojure-filipino (1)
- # clojure-indonesia (1)
- # clojure-my (1)
- # clojure-seattle (2)
- # clojure-sg (1)
- # clojurescript (60)
- # code-reviews (3)
- # conjure (1)
- # cursive (1)
- # datomic (2)
- # figwheel-main (1)
- # fulcro (2)
- # gratitude (1)
- # honeysql (34)
- # lsp (6)
- # malli (5)
- # meander (11)
- # off-topic (27)
- # other-languages (3)
- # play-clj (1)
- # portal (31)
- # sql (13)
- # xtdb (5)
Seeing an indentation issue as noted in the picture: Basically Calva does not indent the function arguments in the picture.
As controlled by cljfmt, like the example here: https://github.com/weavejester/cljfmt/blob/master/README.md#form-depth ?
https://guide.clojure.style/#one-space-indent recommends a single space for indenting function arguments when there are no arguments on the same line as function name
I’m taking a stab at https://github.com/BetterThanTomorrow/calva/issues/1451, so I’ve been trying to find out if there’s already some code in Calva for resolving the project’s source/class path. Apparently there’s no such code yet, is that right? I hope I’m missing something there, otherwise I’ll have to write code for that 😁
I guess I can use
getProjectRootUri and parse either
project.clj at that location, then build the source/class path where I can lookup resources requested by the sideloader.
Thanks, I was searching through clojure-lsp’s source code but couldn’t find anything. I’ll keep looking.
you can use the
rawServerInfo LSP command which calva already uses it somewhere IIRC, it contains a
It's the classpath we need, right? If clojure-lsp can't provide it, we also have deps.clj bundled.
we can easily provide the classpath on
rawServerInfo as we already have that info on clojure-lsp
if you think it makes sense to use I can commit this addition to the output of
Looks like source paths are already included in the server info output, it’s just classpath info like dependency jars, etc, that are not yet included.
Yes, it's a one line fix, I will commit this night to be available on next release and master clojure-lsp
No worries, I was just nosing around the source code:nose: and playing with it a little bit 😄
Thanks a lot @UKFSJSM38! I just ran a quick test here, the classpath is coming out as
nil for me, even when I tap
(:classpath db-value) from inside the
server-info fn. Does this happen to you too? I’m debugging “the clojure way” as described here https://clojure-lsp.io/development/