I’m using Specter (https://github.com/redplanetlabs/specter) in my current project and clj-kondo can’t seem to resolve some of the “navigators” (https://github.com/redplanetlabs/specter/wiki/List-of-Navigators):

the code runs fine, but it seems that the way specter defines them makes it hard for kondo to follow correctly

is there anything i can do to make this work without adding every navigator to my .clj-kondo/config.edn file?

@nbtheduke https://github.com/redplanetlabs/specter#clj-kondo

oops, i am ashamed to have missed that lol

thank you

I think this could be added to the clj-kondo.exports part of the specter lib

then it would have worked almost automatically

but then the maintainer would have to accept that :)

See https://github.com/clj-kondo/clj-kondo/blob/master/doc/config.md#exporting-and-importing-configuration

that’s very cool, thank you

thank you too! added 🙂

Yeah, I added that config a while back @nbtheduke. It may end up eventually needing some more stuff though, so let me know if you run into anything unrecognized or linting weirdly and we can collaborate on that config before making another pr to the repo.

Also @borkdude I asked the author of specter if he wanted to have the config in the artifact and he said no since it increases the size of the artifact (if only slightly) and the number of people who use clj-kondo is still a minority.

Then perhaps contributing it to https://github.com/clj-kondo/config is a good second option

or just do both

I'd be happy to contribute it there if it'd be accepted.

(I mean README + clj-kondo/config)

or link from README to clj-kondo/config

sure

anyway, this will always be an issue (being at the mercy of library maintainers), so clj-kondo/config seems like something which is always possible and perhaps clj-kondo itself could look for config over there automatically in the future

the nice thing about having the config with the library itself is that the config can be maintained per library version

Could have like a --contrib-configs flag when using --copy-configs that'd check for it in this repo.

yeah

Then the repo could become just community-maintained configs that people can use, while still leaving the option for the lib maintainers to publish one that doesn't conflict in the future. I like that idea a lot.

yeah

Micro-release with a bugfix and one new feature by @hugod : https://github.com/clj-kondo/clj-kondo/blob/master/CHANGELOG.md#20210806