This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-01-19
Channels
- # announcements (14)
- # babashka (16)
- # beginners (81)
- # calva (18)
- # chlorine-clover (8)
- # cider (4)
- # clj-kondo (11)
- # cljdoc (4)
- # cljsrn (5)
- # clojure (163)
- # clojure-europe (30)
- # clojure-nl (3)
- # clojure-spec (7)
- # clojure-uk (4)
- # cursive (3)
- # emacs (12)
- # events (1)
- # figwheel-main (3)
- # fulcro (60)
- # introduce-yourself (3)
- # jackdaw (12)
- # juxt (3)
- # lsp (77)
- # malli (23)
- # mid-cities-meetup (9)
- # music (2)
- # off-topic (12)
- # portal (6)
- # releases (2)
- # shadow-cljs (3)
- # spacemacs (7)
- # sql (1)
- # tools-deps (2)
- # vim (3)
Announcement! clojure-extras, an IntelliJ plugin which brings clj-kondo + inline-eval to Cursive, v0.5.0! https://plugins.jetbrains.com/plugin/18108-clojure-extras/https://t.co/SxPSepJaJb It now has an option to analyze the classpath with clj-kondo for better linting results, and more! Join the #clj-extras-plugin to discuss the plugin in detail.
Does this provide support for hooks in any way? Like could i teach cursive about my macros now, or is that functionality still requiring clojure-lsp
I have a library which defines some resources/clj-kondo.exports
.
In a separate application, which uses that library as a dependency, after clojure-lsp initializes and runs clj-kondo stuff I end up with a .clj-kondo/my.lib
folder. However, I don’t have a .clj-kondo/config.edn
in my application, nor in my ~/.config/clj-kondo
directory. It was my impression that a config.edn
containing a {:config-paths ["my/lib"]}
would be required to pull in the lib’s stuff.
Does clj-kondo scan the classpath automatically for resources/clj-kondo.exports` directories, and import them automatically?
@sashton clojure-lsp runs clj-kondo with --copy-configs
while linting your classpath, this is why it copies them to your local config. it also creates a .clj-kondo
dir if doesn't exist yet. in recent versions, clj-kondo automatically loads the exported config from your config dir, so there is no need for :config-paths
anymore for exported configs.
So it sounds like I won’t need to use config-paths
in this case? Or is config-paths
for a separate use-case?
for this case you don't need it, you may still need it in some cases, e.g. when exporting a config for your own library and you would like to use it in linting for the same project
here is an example of that: https://github.com/Engelberg/better-cond/blob/master/.clj-kondo/config.edn