This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2024-07-22
Channels
- # announcements (2)
- # babashka (4)
- # beginners (3)
- # cider (24)
- # clj-kondo (4)
- # clj-on-windows (1)
- # cljs-dev (1)
- # clojure (28)
- # clojure-europe (30)
- # clojure-korea (1)
- # clojure-madison (1)
- # clojure-nl (1)
- # clojure-norway (21)
- # clojure-uk (4)
- # clr (2)
- # core-async (3)
- # cursive (10)
- # datalevin (6)
- # datomic (6)
- # events (1)
- # fulcro (1)
- # hyperfiddle (22)
- # malli (1)
- # off-topic (14)
- # overtone (6)
- # releases (1)
- # rum (5)
- # xtdb (11)
Hello.
I have been using spec
a lot for macros because it's really good at processing arg lists, but it always creates issues when I try to define a macroexpand
hook.
As far as I understand, clj-kondo
's Clojure interpreter used for processing these macroexpansions is deliberately light on dependencies, and I'm not here to ask to change that ofc. What I wanted to know is, did anyone here run into the same issue and find a good solution beyond not using spec
?
how are people dealing with clj-kondo configuration and lots of different repositories? Since most rules really should be shared across multiple (if not all) projects, it would be nice to avoid repeating them everywhere. We could put the config in a scripts repo and symlink it, but it should run the same way locally and on CI. I also wanted to use https://pre-commit.com/ but I don't think I convinced enough colleagues to use that, that would also help with centralising the config. Any other ideas?