hey michiel, have you thought at all about adding "auto-correct" to clj-kondo?

i follow the rubocop releases and they flag certain lints as being able to auto-correct issues, and then also flag certain auto-correctable lints as "unsafe" (potentially changing meaning), and then i spent the weekend thinking about how exactly that might be done with clj-kondo lol

clj-kondo does not auto-correct issues, but it does give precise locations and information so other tools can be built on top which do so, e.g. clojure-lsp has a ton of stuff

this way I can focus on the linting + analysis and don't spend a ton of time on "hey, it doesn't auto-correct correctly, my build is broken" issues

another such tool is https://github.com/oxalorg/clj-konmari/ for example

https://github.com/borkdude/carve is another example

(more stuff here: https://github.com/clj-kondo/clj-kondo/issues/836)

Congrats on your first PR in clj-kondo btw, just merged :)

thank you! so glad and excited to contribute, which is one of the reasons i've been thinking about this stuff

I actually don't use a lot of "auto-correct" stuff myself, usually do it manually

except maybe renaming a local or so, that's where clojure-lsp really comes in handy

You should try "add missing require" code actions @borkdude is the one I most use for sure :)

@ericdallo Nice!