Hi, I am in the process of migrating to duct-core 0.7.0.
I have a usage where a config file uses :duct.core/include
to include yet another file that has a :duct.core/include
. Would I be correct to say that something like this is no longer possible?
You can still nest included files.
@weavejester Thanks for checking! Yes I technically I can, but I don't see it working. Because the old include would merge all the included maps at the same level, but the new include #duct/include
expands the map under a specific key of the config map (which I think only 'works' if it is under a profile key)
I would be more than happy to cook up something minimal to elaborate. Thanks for your attention!
Ah, I see what you mean. Could you pop up a use-case as an issue?
(Just so I don't forget it)
It might be worth making profiles resolve recursively.
It was convenient for reducing the config verbosity for components that were transitively dependent that the top level app would not directly interact
(And thanks for all the work put in to the release 🙏 )