A co-worker is having trouble in VSCode with the bundled clj-kondo linter seeming not to respect a local .clj-kondo/config.edn file

I think plugins in VSCode get the current working directory from the current workspace

So if you’re editing files outside of that, that may not work. Could that be the problem maybe?

I’ll ask her to check

Could also be a typo. Repro welcome.

That’s all it was. Thanks so much

thanks!

@dpassen1 what was it btw, the working dir or the typo?

the working directory

The rest of us on the team either use emacs and flycheck or vim and ale and it has all worked so smoothly for us

there used to be a patch in clj-kondo that when linting a single file it starts looking from the parent dir of that file, but that was only a workaround for a specific editor it might make sense for these cases, but in general the workspace thing works I think

emacs flycheck already sets the working directory to the parent of the file

also the LSP plugin doesn't even see the filename, so it's a bit tricky to apply it in that case. if you know how it works, it's not a problem I reckon

I don't seem to have :import data in the kondo analysis, {c,sh}ould I?

@dominicm I guess we could. PR welcome

there is a namespace clj-kondo.impl.analysis where all data that is collected currently goes through

Cool. Will add to my list 🙂