This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-05-05
Channels
- # announcements (8)
- # babashka (6)
- # beginners (55)
- # biff (8)
- # calva (11)
- # cider (4)
- # clj-kondo (6)
- # cljdoc (23)
- # cljs-dev (22)
- # clojure (89)
- # clojure-brasil (3)
- # clojure-europe (47)
- # clojure-indonesia (1)
- # clojure-nl (1)
- # clojure-spec (3)
- # clojure-uk (5)
- # clojurescript (67)
- # community-development (2)
- # conjure (29)
- # cursive (2)
- # datalog (29)
- # datomic (41)
- # defnpodcast (4)
- # emacs (15)
- # google-cloud (5)
- # holy-lambda (6)
- # hyperfiddle (3)
- # introduce-yourself (8)
- # jobs (1)
- # malli (19)
- # meander (41)
- # nrepl (1)
- # off-topic (30)
- # pathom (22)
- # polylith (30)
- # releases (1)
- # remote-jobs (4)
- # sci (4)
- # shadow-cljs (1)
- # spacemacs (7)
- # specter (3)
- # tools-build (16)
- # tools-deps (2)
I'm setting up a project's clj-kondo config which uses an library that has an exported clj-kondo config. The manual recommends that I use clj-kondo with --copy-configs etc. and then refer to these copied configs via the :config-paths
setting in the project's config.edn. This all works fine but I'm a worried that the libraries exported config will change and so my copy will unwittingly get stale. Do I just have to live with this risk, hoping that any change in the library will result in my stale copied config results in a linting fail, or is there some mechanism I could use to keep my copied config in sync with the library's exported version?
@grahamcarlyle you don't have to set :config-paths
anymore, I should probably remove that. as long as there is a two-level directory like .clj-kondo/foo/bar/config.edn
in there, it will be picked up automatically.
To keep up to date:
clj-kondo --lint $(clojure -Spath) --copy-configs --dependencies --skip-lint
and then check into source control whatever is copied to .clj-kondo/...
except the .cache
directory
@borkdude thanks I will remove my :config-paths
setting. So I have to manually keep the copied config up to date, its a shame that this can't be done automatically by clj-kondo (via some integration with deps or whatever)