This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-09-20
Channels
- # announcements (16)
- # aws (1)
- # babashka (24)
- # beginners (54)
- # calva (25)
- # cider (4)
- # cljs-dev (2)
- # clojure (16)
- # clojure-dev (39)
- # clojure-europe (18)
- # clojure-nl (1)
- # clojure-uk (4)
- # clojurescript (66)
- # core-async (16)
- # cursive (13)
- # datomic (15)
- # deps-new (1)
- # duct (22)
- # fulcro (20)
- # jobs-discuss (1)
- # kaocha (3)
- # lsp (11)
- # malli (8)
- # off-topic (38)
- # other-languages (18)
- # polylith (18)
- # portal (15)
- # react (2)
- # reagent (9)
- # reitit (7)
- # releases (10)
- # reveal (1)
- # sci (13)
- # shadow-cljs (3)
- # specter (4)
- # sql (4)
- # xtdb (16)
One more question, apologies if this is also covered in the docs but I couldn't find it.
I'm looking to create a plugin that adds some default configuration that are common to projects our team works on, including some common plugins. I tried doing this in the config
hook by updating the :kaocha/plugins
value but the plugins inserted this way don't seem to be initialized. Is this doable some way?
It's kind of circular problem—you want your plugin to happen before initialization so the plugins it adds are initialized but if your plugin isn't initialized it can't do anything, so you want it to happen after initialization as well.
Since we use https://cljdoc.org/d/aero/aero/1.1.6/doc/readme to process tests.edn
you could use its #include
to include a default config you share across all projects. You might also be able to create your own reader literal like we did for #kaocha/v1
(https://github.com/lambdaisland/kaocha/blob/a401d2a41ebf2440bc61c83ad782fcdeaaa3fe93/src/kaocha/config.clj#L97). The tricky thing is that I'm pretty sure your reader literal would have to be loaded by Clojure prior to it starting Kaocha and loading the configuration. So you might need a custom runner function. Using #include
seems like the easier and more reliable way.