This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-12-04
Channels
- # adventofcode (100)
- # announcements (7)
- # architecture (1)
- # aws (14)
- # beginners (209)
- # calva (30)
- # cider (5)
- # cljdoc (2)
- # cljs-dev (37)
- # cljsrn (2)
- # clojure (133)
- # clojure-dev (20)
- # clojure-finland (1)
- # clojure-italy (10)
- # clojure-nl (19)
- # clojure-spec (56)
- # clojure-uk (49)
- # clojurescript (57)
- # clojurex (8)
- # core-async (2)
- # core-logic (1)
- # cursive (38)
- # data-science (19)
- # datomic (28)
- # devcards (3)
- # duct (8)
- # emacs (28)
- # figwheel (1)
- # figwheel-main (31)
- # fulcro (2)
- # jobs (1)
- # kaocha (1)
- # klipse (2)
- # mount (6)
- # nrepl (43)
- # off-topic (20)
- # pathom (3)
- # pedestal (1)
- # re-frame (15)
- # ring-swagger (1)
- # shadow-cljs (47)
- # spacemacs (19)
- # sql (20)
- # tools-deps (58)
- # unrepl (13)
- # vim (5)
@weavejester many thanks for your prompt reply. The problem was evicting the duct_hierarchy.edn during the uberjar
I've added :uberjar-merge-with {#"duct_hierarchy\.edn$" leiningen.uberjar/clj-map-merger}
to project.clj
and it works now
I have two keys that use the same configuration (that is, the same map of options). Is there a way to do something like {:foo/a {:my :options} :foo/b #ig/ref-config :foo/a}
? Or what's the correct way to handle something like this?
I could have something like :foo/config {:my :options}
and (defmethod ig/init-key :foo/config [_ _] config)
and then #ig/ref
that, I suppose.
@lambder The lein-duct
plugin should do that for you. Have you removed it?
we have quite specific setup. we have our own lein plugins which may not work with it. I need to check. Thanks for pointing this out.
@flowthing Yes, you can setup the key as a constant. In the latest Duct beta there's also a :duct/const
key you can derive from.