Two ways: • Use clj-kondo as a git dependency • Download a binary from one of the builds

I could make a --dev-build flag to install with the clj-kondo install script maybe, would take a couple of hours of work

babashka install script now supports that

@U04V15CAJ awesome, thank you!

this one?

https://github.com/clj-kondo/clj-kondo/blob/master/doc/install.md

yes, but I was saying that the babashka install script supports --dev-build, the clj-kondo script doesn't yet

(just to be clear)

where can I get that?

define "that"?

What I mean is, babashka supports installing a dev build of babashka in its install script

ah ok, then I misunderstood

for now it's probably easiest to link to a amd linux binary from a recent circleci build

do you have plans to do a release soon again maybe?

I aim for a monthly release since it's a bit of a hassle to release and if I'll do one, the high priority tickets here have to get fixed first: https://github.com/clj-kondo/clj-kondo/projects/1 So I think it's best to either use the git dep or download the pre-built dep from circleci or implement the --dev-build option

The only two changes so far are https://github.com/clj-kondo/clj-kondo/blob/master/CHANGELOG.md#unreleased Compare to the other releases which are often a bit more substantial

alright, I’ll try one of those options

@mkvlr This link should be good: https://output.circle-artifacts.com/output/job/5e6d17d2-f3f3-4123-a521-96639ced7d8b/artifacts/0/release/clj-kondo-2022.12.11-SNAPSHOT-linux-static-amd64.zip

The download is valid for 30 days or so but by the time it invalidates, there will be a new clj-kondo release

🎉

You can do this by making a namespace group based on the name of the namespaces or pattern of the file + config-in-ns https://github.com/clj-kondo/clj-kondo/blob/master/doc/config.md#namespace-groups

Or by separately linting the test dirs with an additional --config argument

ah nice, thanks

Or if this is only for clojure.test :refer :all then you can configure that in config.edn

yep, I did that

for clojure.test it works nicely

except for one case where it doesn’t, curious if you see something wrong there, posted it in the ductile channel

:refer :all is making things a lot more difficult for clj-kondo and static analysis in general, problems are expected with multiple of those

does that also apply to clojure.test or is there special handling for it?

> problems are expected with multiple of those do you mean if referred names overlap or in general? Since kondo does analyze the required namespaces can’t you infer where a name is coming from?

I'll take a look in the ductile channel in a bit

I'm not sure what exactly I should be looking at

This specific case hasn't been covered by clj-kondo, but feel free to post an issue about it

Thanks!

Sure

Bump to stable clj-kondo or a nightly specific kondo version?

nightly, most recent version on master

👍

Done

Should be available on #C032YH7P0R2 soon