@U04V15CAJ i’m running it through

clj-kondo/run! {:cache-dir ".kondo/.cache"
                                       :parallel true
                                       :cache true
                                       :lint files
                                       :config {:output {:analysis true}}})

@domagala.lukas What kind of files are you linting. Just normal source files or .jar files?

@U04V15CAJ both. i’m basically using kondo as a dependency analyzer for function calls to get a deep call graph

if you’re interested in the exact usecase: https://github.com/Cyrik/omni-trace currently working on a feature that lets you make a function call that automatically instruments the call graph, but only that and then removes the instrumentation right after the call. i don’t want to search for the dependencies myself though, since you already did the work for me :)

@domagala.lukas clj-kondo skips dependencies it already linted with :dependencies true . But it doesn't return analysis for those dependencies it skipped. You need to implement your own caching in this case. Just save the analysis information of previously analyzed files somewhere and then combine it with the new analysis.

This is what LSP itself is also doing.

I think you don't even need to lint all the jars every time if you do that, just lint the source the user changed.

yeah that’s what lsp is doing and saving it as a datalevin file, I just didn’t want datalevin as a dependency. was hoping kondo’s cache did the same thing. but yeah you are right, i’ll just do it the same way lsp does it and save it as plain edn. is there a way to run the analysis without running the linting part, since i don’t use that info anyway? or wouldn’t that change much about the run time anyway? thanks for the help btw

it wouldn't change much

but you can turn it off by replacing all linters with level off:

:config {:linters ^:replace {}}