would it be possible for clj-kondo to lint function arguments? eg. (update m k f x) would be an error if f did not take 2 args or x was the wrong type

I need to use a private var on a library, can clj-kondo ignore the error only for a specific var?

no, but if you use #'private/var that works?

It's on clojurescript so it just works.

I'm trying to configure the namespace to ignore the private var linter

Maybe you can do it in the namespace metadata? Not sure if it works for that specific linter

(ns foo "foo docs" {:clj-kondo/config '{:linters {...}}})

I thought that :private-call could be the one but doesn't seems to work.

Can I exclude a single namespace from linting?

this seems to work:

(ns foo "foo docs"
    {:clj-kondo/config '{:linters {:private-call {:level :off}}}})

(clojure.core/is-annotation? 1)

the linter should actually be renamed to :private-var since it should also report usages of private vars. I'll make an issue for that

(I'll make sure it will be non-breaking)

Do I have to use the docstring? I tried without it and it didn't work. Not sure if it makes a difference but the variable I'm using is created by defprotocol.

Actually is a deftype.

no, the docstring is optional.

This works:

(ns bar)

(deftype ^:private Foo [])

(ns foo
  {:clj-kondo/config '{:linters {:private-call {:level :off}}}}
  (:require [bar]))

(clojure.core/is-annotation? 1)
(bar/Foo)

Looks like quoting is mandatory?

yes, Clojure will evaluate your metadata so you have to quote them

I just added the ' and it worked.

🎉

But there is no symbols on it. I cannot see why quoting is necessary in this case.

Thanks!

Because symbols are evaluated by Clojure

oh I see

hmm, yeah, that's weird 🙂

clj-kondo just always expects a quoted value there because most of the time there are symbols in there

it's hard-coded in the linter

Ok, that makes sense. Thanks for the explanation.

Anyone faced getting clj-kondo linter error: unresolved symbol for symbols used in a clj comment macro?

I tried both :exclude on (comment) and (clojure.core/comment), but doesn’t seem to fix it

using latest ver [clj-kondo "2019.12.14"]

@mikerod By default clj-kondo will lint comments as if it's "real" code, because often that's useful during experimentation. But you can turn it off using :skip-comments true

https://github.com/borkdude/clj-kondo/blob/master/doc/config.md#ignore-the-contents-of-comment-forms

oh interesting. I was on that doc page, but didn’t expect it to be a separate option like that

that makes sense, I guess the case I had was somewhat special then. perhaps it should be turned into something more valid to avoid needing this skip.

that option is often useful for CI as well

why CI?

because you don't want to trigger any false alarms in CI?

I see

was thinking there was something special about comment in CI

I see what you’re saying now though