clojure-lsp has a standard of readding a .cljfmt.edn (https://clojure-lsp.io/settings/#all-settings), Since Calva uses clojure-lsp, it could do the same. c/c @U0ETXRFEW

hmm, isn't that for the lein-cljfmt style map instead of just the :indents?

Hum, not sure I understood, for clojure-lsp you could configure any cljfmt config on that file, including :indents

yeah, but the tools.deps version uses command line arguments, like

clojure -Sdeps '{:deps {cljfmt {:mvn/version "0.8.0"}}}' \
  -m cljfmt.main check \
  --indents indentation.clj

hum got it

BTW, any reason why not use clojure-lsp format instead of manually using cljfmt? (https://clojure-lsp.io/api/)

oh, this is much better

perfect!

We replaced at nubank every linter to use only clojure-lsp :)

very nice!

for linting (clj-kondo under the hood), formatting (cljfmt under the hood) and clean-ns (clojure-lsp itself)

with that you could have a common library like codestyle and all services/libs of yours could use the same codestyle configuration

we run multiple jobs like

kondo-check:
  image: "cljkondo/clj-kondo"
  script:
    - clj-kondo --lint src $([ -d test ] && echo "test")

fmt-check:
  image: clojure:openjdk-11-tools-deps-buster
  script:
    - clojure -Sdeps '{:deps {cljfmt/cljfmt {:mvn/version "0.8.0"}}}' -M -m cljfmt.main --indents indentation.edn check

the issue when you run clj-kondo to lint only src and test is that it makes kondo doesn't know the whole classpath and know hooks and custom things for other macros, this issue is fixed with clojure-lsp since it scans the classpath with kondo already

wow, clj-kondo can look for dependencies' configs?

yep :) for example, this library: https://github.com/nubank/state-flow/blob/master/resources/clj-kondo.exports/nubank/state-flow/config.edn

amazing

we just have this on our common codestyle library at nubank:

{:config-paths ["nubank/stateflow" ...]}

then clojure-lsp will already tell to kondo copy the hook and use it, understand this library macros that were configured on the library itself!

the same for midje for example: https://github.com/marick/Midje/blob/master/test-resources/clj-kondo.exports/marick/midje/config.edn

curiously enough the last piece of code I wrote at Nubank was another version of this https://github.com/nubank/state-flow/blob/master/resources/clj-kondo.exports/nubank/state-flow/nubank/state_flow.clj

but never managed to commit it, I think

In case you want to understand how this works: https://github.com/clj-kondo/clj-kondo/blob/master/doc/config.md#exporting-and-importing-configuration

this is awesome

yeah, I can say after we introduced codestyle common library using all those configurations in one single place, we stopped having issues like missing lint config

all services now just use this on .clj-kondo/config.edn:

{:config-paths ["nubank/codestyle"]}

LMK if you need more details

and nubank/codestyle is a lib? config-paths looks for stuff in the classpath?

yes, is just a common lib that in resources has all clj-kondo exports + clojure-lsp exports

yes, in classpath

clojure-lsp has that same feature via :classpath-config-paths settings

the kondo one, search not on classpath, it search on folders :config-paths , but it turns out that you can think on classpath since clojure-lsp will send that to be linted and clj-kondo will copy that config for your service folder

when I created that on clojure-lsp I just added support for classpath only instead of all folder support like kondo has

very very nice

I'll definitely let you know when setting this up!

cool!

I’m not following about all the cool stuff here. Is there a blog write-up somewhere?

Calva doesn’t use clojure-lsp for formatting, anyway, so the question in TS still is relevant. And the answer is no, Calva only knows about one cljfmt config file. You could tell it to read indentation.edn, but then Calva wouldn’t know about your other cljfmt options. It should be quite simple to add this support though. An issue on the repo is welcome!

actually, it seems like defining all the cljfmt options in the leiningen format as it is today should be the way to go. I can then write a workaround or start using clojure-lsp to do my CI checks instead. what do you think?