Replies: 1 comment 1 reply
-
I'm not planning to make breaking changes to the configuration, although I regret some choices here and there :). The options are documented in https://github.com/clj-kondo/clj-kondo/blob/master/doc/config.md and https://github.com/clj-kondo/clj-kondo/blob/master/doc/linters.md. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Context
clojure-emacs/refactor-nrepl#359 (comment) (and also stuff beyond that particular use case)
Problem statement
Different tools might need to be configured essentially the same data.
There isn't a standard format for expressing that, in a DRY manner.
Proposal
Consider
.clj-kondo/config
a "just data" .edn map (as it is already 😄). The nuance being that it would be considered a stable API not to be broken, so that other tools can depend on it.It would be fine by me to consider only a subset of this config a "public API". The stable keys could be reflected on a doc or such.
There might also be a helper (related to #1555) that reads config and trims everything not in the "public API" whitelist.
Alternatives
Coordinate tooling authors for agreeing on a common .edn format and/or inline metadata.
Cheers - V
Beta Was this translation helpful? Give feedback.
All reactions