The clj-kondo analysis dump can include one or more entries per repo, depending on how many bases (deps.edn, project.clj, etc.) the project has. The difference is represented through a top-level :basis key in each of the maps in the file.
Since the :basis key is not a part of clj-kondo's own output, I think it would be helpful to document it for Dewey users, and to explain its impact on the cardinality between repos and analysis maps in the pre-computed analysis.edn dumps. I initially assumed that each repo would have just a single analysis entry.
The clj-kondo analysis dump can include one or more entries per repo, depending on how many bases (
deps.edn
,project.clj
, etc.) the project has. The difference is represented through a top-level:basis
key in each of the maps in the file.Since the
:basis
key is not a part of clj-kondo's own output, I think it would be helpful to document it for Dewey users, and to explain its impact on the cardinality between repos and analysis maps in the pre-computedanalysis.edn
dumps. I initially assumed that each repo would have just a single analysis entry.