clj-kondo 2026-09-29

`clj-kondo` plus polylith

We are using both of them and since we have multiple implementations of the same namespace, and clj-kondo does not like the redefined namespaces we have an issue

clj-kondo is integrated to our git pre-commit hooks and whenever we change something in both places clj-kondo screams

What is the best practice to handle such cases?

how many clj-kondo configs do you have per polylith workspace?

👋 2

We have one global config

Read, we don't have a separate config per workspace or per brick or anything like that

I would consider maintaining one per polylith project (including the dev project) instead, which means many per workspace. They can share most of the configuration, but cache and linting should be per "classpath definition" if I'm not wrong

Where I discussed this as clj-kondo support arrived in Cursive and the 👧 monorepo I'm maintaining with one top-level config started to behave strange

Thanks, Imre

Do share your experience if you can, I haven't migrated mine yet 😅

Sure, but since it is not that urgent, so I don't know when I'll get back to this

Hey Imre! 👋 We are also lookng for making this potentially runtime pluggable (similar to Terraform Providers)