Since clojure-lsp public linters now lives in clj-kondo config, clojure-lsp needs to check that in other features like code lens which check that same config key

exposing that would help a lot

(Actually I'm using that impl ns ATM)

ah

but the config is already part of run!, isn't this enough?

but I don't need that config, I need the one in user project root or in the home one

like the final config

the "final" config is the one in run!

it's the one that clj-kondo really used

oh, yes, that would partially work, but I'd like to make something that doesn't need to restart the server, like check everytime to see if the config changed

so tell me, regardless of the impl function, "I need a function foo that given argument x returns y", then what would this be?

something like (clj-kondo.core/config project-root) which brings the merged edn of home user clj-config + project clj-kondo config

just making that impl public would work as I'm doing something like:

(defn kondo-config [db]
  (kondo.core-impl/resolve-config (io/file (:project-root-uri db)) {}))

sorry, you have to be more specific. the merged config is already in the output of run! so I don't understand what you're missing yet

Sorry, let me try to be more specific • user has lsp running in a project • user change clj-kondo/.config of that project or its clj-kondo home dir config changing the :linters clojure-lsp/unusued-public-var setting, adding a exclude or something • next time clojure-lsp process code lens for that file, it will call this new function which would bring the config

we could update the db with clj-kondo output of run!

but that would need user to edit the file

to clojure-lsp run kondo there

so you are watching these files?

yeah, not really, you are right, the next time code lens need to be calculated kondo would run as well

I'll use the output of run! and test if it works 🙂 thanks!

It worked perfectly 🙂