Error looking up classpath info in ClojureScript projects

[PEZ]

I think between 146 and 148 it has started to pop up a message about _ Error looking up classpath info_ when clojure-lsp starts in ClojureScript projects.

I can't see that it affects how Calva works.

[bpringe]

This was added by @ericdallo to clojure-lsp after we discussed it. Basically, if the classpath lookup fails, clojure-lsp will not work properly. We've had a user or two already wonder what was going on and we had to debug with them to find this info in the logs. This way it's immediately apparent that something is wrong, and they aren't confused why things aren't working.

[ericdallo]

Exactly ☝🏻 , @PEZ check your /tmp/clojure-lsp.out log for more info on why this lookup failed

[bpringe]

I was typing what Eric said above, basically 😄. There could be something that needs to be better defaulted in clojure-lsp for certain typical clojurescript setups, or you may have a non-typical setup and need to add something to your .lsp/config.edn :project-specs -> :classpath-cmd.

[ericdallo]

Yes I suspect, since I'm not a clojurescript developer I don't know the common setup for it, if you know or have any suggestion let me know

[PEZ]

i think the message, the way it is delivered, makes it feel like something is broken. Before i realized things were actually working I restarted, then reinstalled vs code.

[bpringe]

@ericdallo Maybe it should be a warning instead of an error, worded like "Classpath lookup failed in clojure-lsp. Some features may not work correctly." Just a thought.

It is true though, in a way, that something is broken. Some things won't work.

[ericdallo]

Actually, without a successful classpath lookup, things like find definition on jars may not work

[ericdallo]

Yes, I can change that

[ericdallo]

clojure-lsp/clojure-lsp#246