duct

lambder 2018-12-04T09:23:11.008100Z

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

lambder 2018-12-04T09:23:41.008500Z

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

flowthing 2018-12-04T09:53:10.010200Z

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?

flowthing 2018-12-04T09:53:51.010900Z

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

2018-12-04T21:59:47.011700Z

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

lambder 2018-12-04T22:01:01.013Z

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.

2018-12-04T22:01:09.013200Z

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