This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-01-13
Channels
- # announcements (2)
- # architecture (10)
- # aws (1)
- # babashka (1)
- # beginners (208)
- # calva (15)
- # clojure (164)
- # clojure-australia (9)
- # clojure-europe (37)
- # clojure-nl (19)
- # clojure-sanfrancisco (2)
- # clojure-spec (10)
- # clojure-taiwan (2)
- # clojure-uk (48)
- # clojurescript (59)
- # conjure (2)
- # core-async (3)
- # data-science (3)
- # datomic (5)
- # events (66)
- # figwheel-main (2)
- # fulcro (35)
- # graphql (3)
- # jobs-rus (3)
- # kaocha (1)
- # meander (5)
- # off-topic (85)
- # pedestal (2)
- # re-frame (5)
- # reitit (11)
- # reveal (5)
- # shadow-cljs (16)
- # slack-help (15)
- # test200 (4)
- # tools-deps (12)
- # xtdb (9)
Calva version 2.0.150 is released. 🎉 
In this version linting is now provided from clojure-lsp (powered by clj-kondo), and the clj-kondo extension is no longer bundled with Calva. When you upgrade you'll likely see a warning advising to uninstall the clj-kondo extension to avoid some duplicate lint reports.
9This 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.
@brandon.ringe Is this configurable for clojure-lsp users (either to use clj-kondo via lsp or via the extension by enabling it)?
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.
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
I basically want people to specify a clj-kondo version with their bug reports, that's what it comes down to
fyi the version is available on the classpath as (slurp (io/resource "CLJ_KONDO_VERSION"))
Yeah, we can do that 🙂 @U04V15CAJ via clj-kondo is there any function to retrieve clj-kondo version?