Fork me on GitHub
#calva
<
2021-01-13
>
bringe22:01:45

This should also reduce memory usage on your machine since the clj-kondo extension's lsp server will no longer be running once you uninstall the extension.

đź‘Ť 1
borkdude22:01:49

@brandon.ringe Is this configurable for clojure-lsp users (either to use clj-kondo via lsp or via the extension by enabling it)?

bringe22:01:31

They cannot disable diagnostics from clojure-lsp, and only receive them from the clj-kondo extension. They can use both if they're okay with some duplicate linting messages. > configurable for clojure-lsp users Not sure what is meant here, but usage of clojure-lsp through Calva is not optional. If there would be a good reason to disable clojure-lsp's diagnostics, it would be easy to add a setting for it.

borkdude22:01:01

The reason I'm asking is that I regularly get bug reports and it would be good if the version of clj-kondo was communicated or if there was some means to get the raw clj-kondo output without a tool in between

borkdude22:01:06

I basically want people to specify a clj-kondo version with their bug reports, that's what it comes down to

pez22:01:13

We can request that clojure-lsp includes this in the server-info message.

pez22:01:51

The version of clj-kondo, I mean.

borkdude22:01:56

fyi the version is available on the classpath as (slurp (io/resource "CLJ_KONDO_VERSION"))

ericdallo22:01:57

Yeah, we can do that 🙂 @U04V15CAJ via clj-kondo is there any function to retrieve clj-kondo version?

bringe23:01:30

I see, sounds good!