does clj-kondo respect type hints for non-primitives when linting function calls?

(defn ^DBObject find-one
  "Returns a single DBObject from this collection matching the query."
  ([^DB db ^String coll ^Map ref]
     (.findOne (.getCollection db (name coll))
               (to-db-object ref))))

if you hint it as a string, clj-kondo will think you will have to pass a string or nil there.

any way I can disable this?

why would you add a type hint that doesn't do anything?

i didn’t write the library, so I don’t know lol

you're trying to solve lint warnings in libraries?

oh I get it, you're calling the function and then get the lint warning

you can override this with {:linters`{:type-mismatch {:namespaces {library {function {:arities {3 {:args [:any :any :any]}}}}}}}}`

cool, thank you.

the exact format is here: https://github.com/clj-kondo/clj-kondo/blob/master/doc/types.md

In a hook, what’s the best way of adding clj-kondo suppression of certain lints (on the re-written code)? The re-written code defines some things that may not be used.

emit code that uses the things

just a vector with the things for example

of course, that works - thanks

For clj-kondo integration with emacs, there are three possibilities - flycheck-clj-kondo, anakondo, and flymake-kondor. IS there are clear recommendation from the community as to which one is preferred?

If you already use flycheck, flycheck-clj-kondo

@chris441 I'm using and maintaining flycheck-clj-kondo myself. But I'm also using clojure-lsp. If I wasn't maintaining clj-kondo myself, I might not be using flycheck-clj-kondo since clojure-lsp already packages clj-kondo.

But as I'm always on the latest master, I'm using flycheck-clj-kondo separately from clojure-lsp.

flymake is built in to emacs, so some people prefer that. especially if they’re using eglot

@chris441 check https://clojure-lsp.io/features/, clojure-lsp uses kondo under the hood

Right, so reading into those answers a bit perhaps using lsp-mode for emacs is also a recommended pathway. Especially since the point of this work is to enable a smoothr \flo

sorry, baby typing

flow for calva users and tmd.

Then, is there a different setup you use if you are going to be configuring kondo hooks and such? Like I guess just running kondo from the command line?

@chris441 with clojure-lsp there is no need to run clj-kondo from the command line

Including when debugging config macro definitions?

for debugging, I would use the command line and println

but for seeing feedback in the editor from your hooks using clojure-lsp should be enough

@dpassen1 - I currently intermittently use flycheck-joker. But I want to integrate correct clj-kondo hooks into our stack which is kind of extensive so switching that portion of my system is the just not a big deal work-wise as compared to the actual work of going through each library and updating it so the various macros used to define the interfaces are correctly represented in clj-kondo.

What is the relationship between emacs lsp-mode and clojure-lsp?

Well, and clj-kondo.lsp?

lsp-mode is the emacs lsp client

clojure-lsp is the clojure lsp server

and clj-kondo.lsp is an lsp server which only provides clj-kondo and nothing else

if you use clojure-lsp, you don't need to install clj-kondo or use clj-kondo.lsp

Perfect, this all makes sense. Thanks everyone (bork, eric, derek) for the help.

Is it possible to return a valid :keywords analysis for this code 🧵 ?