duct

iku000888 2019-01-18T03:22:07.008800Z

Hi, I am in the process of migrating to duct-core 0.7.0.

iku000888 2019-01-18T03:23:36.010300Z

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?

2019-01-21T04:33:35.013800Z

You can still nest included files.

iku000888 2019-01-23T04:05:56.043Z

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

iku000888 2019-01-23T04:06:17.043200Z

I would be more than happy to cook up something minimal to elaborate. Thanks for your attention!

2019-01-23T14:12:13.046700Z

Ah, I see what you mean. Could you pop up a use-case as an issue?

👍 1
2019-01-23T14:13:59.046900Z

(Just so I don't forget it)

2019-01-23T14:14:17.047100Z

It might be worth making profiles resolve recursively.

iku000888 2019-01-25T07:50:37.048800Z

https://github.com/duct-framework/core/issues/19 🙇

iku000888 2019-01-18T03:24:58.011500Z

It was convenient for reducing the config verbosity for components that were transitively dependent that the top level app would not directly interact

iku000888 2019-01-18T03:25:24.012Z

(And thanks for all the work put in to the release 🙏 )