This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-07-13
Channels
- # aleph (15)
- # announcements (4)
- # babashka (36)
- # babashka-sci-dev (1)
- # beginners (15)
- # biff (2)
- # calva (15)
- # cider (3)
- # clj-kondo (8)
- # clojure (149)
- # clojure-europe (14)
- # clojure-norway (13)
- # clojure-switzerland (1)
- # clojure-uk (1)
- # clojurescript (21)
- # community-development (5)
- # cursive (20)
- # data-science (2)
- # datomic (7)
- # duct (5)
- # emacs (19)
- # etaoin (3)
- # events (2)
- # fulcro (11)
- # introduce-yourself (2)
- # jobs (4)
- # jobs-discuss (19)
- # joyride (1)
- # leiningen (11)
- # malli (7)
- # membrane (131)
- # nbb (12)
- # nginx (1)
- # off-topic (33)
- # pathom (8)
- # polylith (28)
- # re-frame (8)
- # sci (7)
- # shadow-cljs (225)
- # spacemacs (10)
- # specter (1)
- # vim (10)
- # xtdb (8)
What arguments do I need to use with clj-kondo to lint a project deps.edn
, resources/config.edn
, clojure .clj files under src
and test
directory trees, but not the file .cljstyle
in the root directory of the project.
I’ve looked at include exclude, but getting only a sub-set of the files linted
Do I need to run separate clj-kondo --lint files for each? So 4 different clj-kondo commands?
@U05254DQM You can probably just do clj-kondo --lint .
right? Files that don't end with .clj
etc are skipped
ah, so I can just chain the paths with --lint, that sounds good…
Is there an option to list what files are being checked
Yes, the command line works, thanks.
I was getting tripped up with a GitHub action that sets a *.clj*
pattern for clj-kondo by default. Hopefully I can over-ride this in the GitHub action and simulate the command line correctly
In the end I’ve switched to the clojure-setup GitHub action and used the following command to avoid linting the clojure files under dev directory
clj-kondo --lint deps.edn resources/config.edn src test --config .clj-kondo/config-ci.edn
Works very nicely, thank you.