i use clj-kondo in my CI and rely on failure to inform when my hooks might be incorrect lol

@U04CAPVN1HS You could use clj-kondo as a JVM library and just test for :findings that it should report when you run! over some example code?

Nice @UEENNMX0T! So you call clj-kondo in a shell script iterating over several test scenario input files and expected all them to exit code 0?

@U04V15CAJ hmmm to use clj-kondo as a JVM library... very interesting!

Yes, in the JVM you can also call the hooks-api in the REPL :)

I don't do anything extra, I just write what looks like a valid hook and then try it out a bunch and then rely on normal clj-kondo --parallel --lint dev src test to tell me when i've made a mistake (either in code or in the hook).

oh, got it 😉

thanks @UEENNMX0T and @U04V15CAJ! insightful tips!