You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's possible I'm just missing this and it's already possible, but it seems like cljfmt currently doesn't support a way to split up the config across multiple files?
clj-kondo supports projects exporting their own configs, such that downstream projects can import and make use of them. This sort of feature seems like it would be super helpful in cljfmt as well!
For example, a utility library that defines a common macro used by lots of projects could specify a cljfmt.edn, and downstream projects could choose to import and merge that config into their own root config in some way.
It wouldn't even necessarily have to be as complicated as what clj-kondo has, simply being able to specify other config files in your root config file, and having all the configs deep-merged into one seems like it would be a useful first step to me.
Something like being to specify this in your config.edn:
I don't believe there's any support for this currently. Allowing cljfmt to find config files on the classpath would be useful functionality. An :extra-configs or :include-configs key might also be useful.
It's possible I'm just missing this and it's already possible, but it seems like cljfmt currently doesn't support a way to split up the config across multiple files?
clj-kondo supports projects exporting their own configs, such that downstream projects can import and make use of them. This sort of feature seems like it would be super helpful in cljfmt as well!
For example, a utility library that defines a common macro used by lots of projects could specify a cljfmt.edn, and downstream projects could choose to import and merge that config into their own root config in some way.
It wouldn't even necessarily have to be as complicated as what clj-kondo has, simply being able to specify other config files in your root config file, and having all the configs deep-merged into one seems like it would be a useful first step to me.
Something like being to specify this in your config.edn:
The text was updated successfully, but these errors were encountered: