This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-11-20
Channels
- # babashka (56)
- # beginners (151)
- # calva (3)
- # cider (31)
- # clj-kondo (17)
- # cljs-dev (5)
- # clojure (26)
- # clojure-australia (21)
- # clojure-dev (7)
- # clojure-europe (23)
- # clojure-nl (5)
- # clojure-spec (54)
- # clojure-uk (11)
- # clojuredesign-podcast (8)
- # clojurescript (77)
- # community-development (10)
- # core-typed (1)
- # cursive (3)
- # datomic (7)
- # docker (67)
- # emacs (10)
- # expound (6)
- # figwheel-main (3)
- # graalvm (67)
- # helix (10)
- # java (13)
- # jobs (6)
- # kaocha (4)
- # leiningen (15)
- # malli (2)
- # meander (31)
- # off-topic (40)
- # pedestal (9)
- # rdf (7)
- # reagent (5)
- # reitit (9)
- # remote-jobs (5)
- # shadow-cljs (94)
- # sql (7)
- # testing (12)
- # tools-deps (75)
- # vim (13)
When using several :config-paths
is it expected that configs for :unresolved-symbol
, :deprecated-var
, :output
to merge/concatenate?
I may be doing something wrong then. I have a monorepo and on the toplevel I added a config to make my editor happy. I was trying to only have :config-paths
pointing to the subprojects configs. But when I deleted the rest of the configuration on the toplevel warnings started to show on the editor.
@mynomoto if you could make a small github repo that mimics your problem, I'd be happy to take a look. You can probably make deliberate mistakes in the config and they will get logged as warnings, to see if they are being processed at all
@mynomoto Note that clj-kondo will only look up one time for a .clj-kondo directory. .clj-kondo directories on a higher level won't be seen
so if you have a .clj-kondo in your subrepo and one on the top-level, only the subrepo one will be considered
Is there a way to see the config that is being used after the :config-paths
are processed?
not currently, but you could try with clj-kondo in the JVM and stick a println somewhere in clj-kondo/impl/config.clj