Alex Whitt

Re-reading your earlier responses, I see that's what you said would be the needed solution. Is that difficult or error-prone, or might it have unwanted side-effects? Or is it a...

OK, I can definitely see the difficulty. You know what though, I totally forgot about `duct.core.merge/displace`, and it seems to be sufficient for me in conjunction with top-level keys. I...

Thank you for being so attentive to my questions! I wish all open source maintainers were as on the ball as you are.

I'm revisiting this issue because I'm now thinking about a use case where, depending on the profile, some modules may or may not be desired. It's totally possible to just...

Whoops didn't actually include an actual question in there! The basic question is this: Is there a good, data-driven way to turn these various features/modules/interfaces on and off, other than...

I'm hoping we can come up with a nice, intuitive solution, but until then I'm getting by doing the kinds of workarounds we've been discussing.

I got bitten by this again. My module needs to add different keys to the system based on config that changes per profile, and I don't think that's possible with...

Moving the `:myproj/module` config directly to local.edn (without the `#ig/ref`) allows the system to load, but `:myproj/module` doesn't actually get applied.

That would be a huge step forward. Ideally you wouldn't need the `:components` and `:modules` submaps, but if it substantially reduces the complexity, then I certainly don't mind the extra...

I spent a bunch of time trying to figure out how to do this conversion with this library until I found this issue. Any chance this could be resolved at...