Fork me on GitHub
#duct
<
2018-12-04
>
lambder09:12:11

@weavejester many thanks for your prompt reply. The problem was evicting the duct_hierarchy.edn during the uberjar

lambder09:12:41

I've added :uberjar-merge-with {#"duct_hierarchy\.edn$" leiningen.uberjar/clj-map-merger} to project.clj and it works now

flowthing09:12:10

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?

flowthing09:12:51

I could have something like :foo/config {:my :options} and (defmethod ig/init-key :foo/config [_ _] config) and then #ig/ref that, I suppose.

weavejester21:12:47

@lambder The lein-duct plugin should do that for you. Have you removed it?

lambder22:12:01

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.

weavejester22:12:09

@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.

flowthing06:12:01

:duct/const did the trick, thanks!