When using several :config-paths is it expected that configs for :unresolved-symbol, :deprecated-var, :output to merge/concatenate?

yes, all the configs merge

does this give a problem?

you can prevent merging / override by putting ^:replace on a map value

^ @mynomoto

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

Ok, thanks. I will try to investigate/reproduce on a small project.

oh btw, you might be able to see the config when you use clj-kondo.core

as a JVM lib

as output from run!

user=> (require '[clj-kondo.core :as k])
nil
user=> (keys (k/run! {:lint ["src"]}))
(:findings :config :summary)

Ok, thanks. I will try that.