Table of contents:
Clj-kondo can be configured in five ways, by providing:
- home dir config in
~/.config/clj-kondo/config.edn
(respectsXDG_CONFIG_HOME
) - project config: a
config.edn
file in the.clj-kondo
directory (see project setup) :config-paths
in projectconfig.edn
: a list of directories that provide additional config- command line
--config
file or EDN arguments - namespace local config using
:clj-kondo/config
metadata in the namespace form
The configurations are merged in the following order, where a later config overrides an earlier config:
- home dir config
:config-paths
in project config- project config
- command line config
- namespace local config
The ^:replace
metadata hint can be used to replace parts or all of the
configuration instead of merging with previous ones. The home dir config is
implicitly part of :config-paths
. To opt out of merging with home dir config
use :config-paths ^:replace []
in your project config.
Note that namespace local config must always be quoted: {:clj-kondo/config '{:linters ...}}
and quotes should not appear inside the config.
Look at the default configuration for all available options.
See the config project for library-specific configurations.
Clj-kondo only expands a selected set of macros from clojure.core and some popular community libraries. For unrecognized macros you can use these configurations:
$ echo '(select-keys [:a])' | clj-kondo --lint -
<stdin>:1:1: error: wrong number of args (1) passed to clojure.core/select-keys
linting took 10ms, errors: 1, warnings: 0
$ echo '(select-keys [:a])' | clj-kondo --lint - --config '{:linters {:invalid-arity {:level :off}}}'
linting took 10ms, errors: 0, warnings: 0
Some linters are not enabled by default. Right now these linters are:
:missing-docstring
: warn when public var doesn't have a docstring.:unsorted-required-namespaces
: warn when namespaces in:require
are not sorted.:refer
: warn when there is any usage of:refer
in your namespace requires.:single-key-in
: warn when using assoc-in, update-in or get-in with single key.:shadowed-var
: warn when a binding shadows a var.
You can enable these linters by setting the :level
:
{:linters {:missing-docstring {:level :warning}}}
You can accomplish this by using ^:replace
metadata, which will override
instead of merge with other configurations:
$ clj-kondo --lint corpus --config '^:replace {:linters {:redundant-let {:level :info}}}'
corpus/redundant_let.clj:4:3: info: redundant let
corpus/redundant_let.clj:8:3: info: redundant let
corpus/redundant_let.clj:12:3: info: redundant let
To ignore all warnings in an expression, place a hint before it. It uses reader comments, so they won't end up in your runtime.
#_:clj-kondo/ignore
(inc 1 2 3)
To ignore warnings from just one or a few linters:
#_{:clj-kondo/ignore [:invalid-arity]}
(inc 1 2 3)
To ignore warnings for only one language in a reader conditional:
#_{:clj-kondo/ignore #?(:clj [:unused-binding] :cljs [])}
(defn foo [x]
#?(:cljs x)) ;; x is only used in cljs, but unused is ignored for clj, so no warning
In the following code the my-defn
macro is defined, but clj-kondo doesn't know how to interpret it:
(ns foo)
(defmacro my-defn [name args & body]
`(defn ~name ~args
(do (println "hello!")
~@body)))
(my-defn foo [x])
Hence (foo 1 2 3)
will not lead to an invalid arity error. However, the syntax
of my-defn
is a subset of clojure.core/defn
, so for detecting arity errors
we might have just linted it like that. That is what the following configuration accomplishes:
{:lint-as {foo/my-defn clojure.core/defn}}
When you have custom def
or defn
-like macros and you can't find a supported macro that is like it, you can use:
{:lint-as {foo/my-defn clj-kondo.lint-as/def-catch-all}}
In the following code streams
is a macro that assigns a special meaning to the symbol where
, so it should not be reported as an unresolved symbol:
(ns foo
(:require [riemann.streams :refer [streams]]))
(def email (mailer {:host "mail.relay"
:from "[email protected]"}))
(streams
(where (and (= (:service event) “my-service”)
(= (:level event) “ERROR”))
,,,))
This is the config for it:
{:linters
{:unresolved-symbol
{:exclude [(riemann.streams/streams [where])]}}}
To exclude all symbols in calls to riemann.streams/streams
write :exclude [(riemann.streams/streams)]
, without the vector.
To exclude a symbol from being reported as unresolved globally in your project, e.g. foo
, you can use :exclude [foo]
.
Sometimes vars are introduced by executing macros, e.g. when using HugSQL's def-db-fns
. You can suppress warnings about these vars by using declare
. Example:
(ns hugsql-example
(:require [hugsql.core :as hugsql]))
(declare select-things)
;; this will define a var #'select-things:
(hugsql/def-db-fns "select_things.sql")
(defn get-my-things [conn params]
(select-things conn params))
If the amount of symbols introduced by HugSQL becomes too unwieldy, consider
introducing a separate namespace in which HugSQL generates the vars:
foo.db.hugsql
. You can then refer to this namespace from foo.db
with
(require '[foo.db.hugsql :as sql]) (sql/insert! ...)
and clj-kondo will not
complain about this.
Furthermore, the :lint-as
option can help treating certain macros like
built-in ones. This is in clj-kondo's own config:
:lint-as {me.raynes.conch/programs clojure.core/declare
me.raynes.conch/let-programs clojure.core/let}
and helps preventing false positive unresolved symbols in this code:
(ns foo (:require [me.raynes.conch :refer [programs let-programs]]))
(programs rm mkdir echo mv)
(let-programs [clj-kondo "./clj-kondo"]
,,,)
(ns foo
{:clj-kondo/config '{:linters {:unresolved-namespace {:exclude [criterium.core]}}}})
(criterium.core/quick-bench [])
Some macros rewrite their arguments and therefore can cause false positive arity errors. Imagine the following silly macro:
(ns silly-macros)
(defmacro with-map [m [fn & args]]
`(~fn ~m ~@args))
which you can call like:
(silly-macros/with-map {:a 1 :d 2} (select-keys [:a :b :c])) ;;=> {:a 1}
Normally a call to this macro will give an invalid arity error for (select-keys [:a :b :c])
, but not when you use the following configuration:
{:linters {:invalid-arity {:skip-args [silly-macros/with-map]}}}
In the following code, the namespaces foo.specs
and bar.specs
are only loaded for the side effect of registering specs, so we don't like clj-kondo reporting those namespaces as required but unused.
(ns foo (:require [foo.specs] [bar.specs]))
(defn my-fn [x] x)
That can be done using this config:
{:linters {:unused-namespace {:exclude [foo.specs bar.specs]}}}
A regex is also supported:
{:linters {:unused-namespace {:exclude [".*\\.specs$"]}}}
This will exclude all namespaces ending with .specs
.
Imagine you want to have taoensso.timbre/debug
available in all of your
namespaces. Even when you don't use it, you don't want to get a warning about
it. That can be done as follows:
{:linters {:unused-referred-var {:exclude {taoensso.timbre [debug]}}}}
Say you have the following function:
(ns app.foo)
(defn foo {:deprecated "1.9.0"} [])
and you still want to be able to call it without getting a warning, for example in function in the same namespace which is also deprecated:
(defn bar {:deprecated "1.9.0"} []
(foo))
or in test code:
(ns app.foo-test
(:require
[app.foo :refer [foo]]
[clojure.test :refer [deftest is]]))
(deftest foo-test [] (is (nil? (foo))))
To achieve this, use this config:
{:linters
{:deprecated-var
{:exclude
{app.foo/foo
{:defs [app.foo/bar]
:namespaces [app.foo-test]}}}}}
A regex is also permitted, e.g. to exclude all test namespaces:
{:linters {:deprecated-var {:exclude {app.foo/foo {:namespaces [".*-test$"]}}}}}
To exclude unused bindings from being reported, start their names with
underscores: _x
. To exclude warnings about key-destructured function arguments, use:
{:linters {:unused-binding {:exclude-destructured-keys-in-fn-args true}}}
Examples:
$ echo '(defn f [{:keys [:a :b :c]} d])' | clj-kondo --lint -
<stdin>:1:18: warning: unused binding a
<stdin>:1:21: warning: unused binding b
<stdin>:1:24: warning: unused binding c
<stdin>:1:29: warning: unused binding d
linting took 8ms, errors: 0, warnings: 4
$ echo '(defn f [{:keys [:a :b :c]} _d])' | clj-kondo --lint - --config \
'{:linters {:unused-binding {:exclude-destructured-keys-in-fn-args true}}}'
linting took 8ms, errors: 0, warnings: 0
The exclude the :as
binding from being reported (which can be useful for
self-documenting some code), use:
{:linters {:unused-binding {:exclude-destructured-as true}}}
Examples:
$ echo '(defn f [{:keys [a b c] :as g}] a b c)' | clj-kondo --lint - --config \
'{:linters {:unused-binding {:exclude-destructured-as false}}}'
<stdin>:1:29: warning: unused binding g
linting took 46ms, errors: 0, warnings: 1
$ echo '(defn f [{:keys [a b c] :as g}] a b c)' | clj-kondo --lint - --config \
'{:linters {:unused-binding {:exclude-destructured-as true}}}'
linting took 56ms, errors: 0, warnings: 0
Example code:
(ns foo) (defn- f [])
Example config:
{:linters {:unused-private-var {:exclude [foo/f]}}}
Sometimes it's desirable to have a consistent alias for certain namespaces in a project. E.g. in the below code it could be desirable if every alias for old.api
was old-api
:
(ns foo (:require [new.api :as api]))
(ns bar (:require [old.api :as old-api]))
(ns baz (:require [old.api :as api]))
This configuration:
{:linters {:consistent-alias {:aliases {old.api old-api}}}}
will give this warning:
Inconsistent alias. Expected old-api instead of api.
If you prefer not to lint the contents of (comment ...)
forms, use this configuration:
{:skip-comments true}
{:linters {:refer-all {:exclude [alda.core]}}}
The :shadowed-var
linter warns when a binding shadows a var.
Example config:
{:linters {:shadowed-var {:level :warning
:exclude [ns]
:suggest {name nom}}}}
(fn [name] name)
^--- Shadowed var: clojure.core/name. Suggestion: nom
Use :exclude
to suppress warnings for specific binding names. To avoid
shadowing core vars use :refer-clojure
+ :exclude
in the ns
form.
See hooks.md.
$ clj-kondo --lint corpus --config '{:output {:format :json}}' | jq '.findings[0]'
{
"type": "invalid-arity",
"filename": "corpus/nested_namespaced_maps.clj",
"row": 9,
"col": 1,
"level": "error",
"message": "wrong number of args (2) passed to nested-namespaced-maps/test-fn"
}
Printing in EDN format is also supported.
$ clj-kondo --lint corpus --config '{:output {:pattern "::{{level}} file={{filename}},line={{row}},col={{col}}::{{message}}"}}'
::warning file=corpus/compojure/core.clj,line=2,col=19::Unsorted namespace: foo
The custom pattern supports these template values:
Template Variable | Notes |
---|---|
{{filename}} |
File name |
{{row}} |
Row where linter violation starts |
{{col}} |
Column where linter violation starts |
{{level}} |
Lowercase level of linter warning, one of info,warn,error |
{{LEVEL}} |
Uppercase variant of {{level}} |
{{message}} |
Linter message |
$ clj-kondo --lint "$(clj -Spath)" --config '{:output {:include-files ["^clojure/test"]}}'
clojure/test.clj:496:6: warning: redundant let
clojure/test/tap.clj:86:5: warning: redundant do
linting took 3289ms, errors: 0, warnings: 2
$ clj-kondo --lint "$(clj -Spath)" --config '{:output {:include-files ["^clojure/test"] :exclude-files ["tap"]}}'
clojure/test.clj:496:6: warning: redundant let
linting took 3226ms, errors: 0, warnings: 1
$ clj-kondo --lint "$(clj -Spath)" --config '{:output {:progress true}}'
.................................................................................................................
cljs/tools/reader.cljs:527:9: warning: redundant do
(rest of the output omitted)
The config '{:output {:canonical-paths true}}'
will output canonical file
paths (absolute file paths without ..
). This also shows the full path of a jar
file when you lint a classpath.
$ clj-kondo --lint corpus --config '{:output {:canonical-paths true}}'
/Users/borkdude/dev/clj-kondo/corpus/cljc/datascript.cljc:8:1: error: datascript.db/seqable? is called with 2 args but expects 1
(rest of the output omitted)
These are some example configurations used in real projects. Feel free to create a PR with yours too.
Also see the config project.
Some configuration keys have been renamed over time. The default configuration is always up-to-date and we strive to mantain backwards compatibility. However, for completeness, you can find a list of the renamed keys here.
:if -> :missing-else-branch