anotherjames
commented
8 years ago Unrelated thought btw ... Unless it's not too difficult to implement/maintain, I wonder if we should just drop support for config across multiple modules/buckets?
If it can be done, it would be nice, but I can see it getting tricky when it comes to exporting dependencies, as if module A and module B both have a particular dependency, how do we handle that? Does the config get exported to both, do we arbitrarily pick one? (And the same probably applies to dependants too.)
A 'solution' could be to only support exporting dependencies/dependants when working with just the one module. But that is more or less what we've already got - so I wonder if we should just consider all the work in this PR as a cm_config_tools 'version 2.0' (i.e. 8.x-2.x). That would allow any projects that need that possibility could remain on 1.0, without nice dependency management. And then in future, if we can think of a better solution, that can be added on top of either 'version', or as a 3.0 if it can't really be backwards-compatible.
@stevetweeddale and @darthsteven what do you think of that as a plan? I'm not raising this to unquestionably encourage us to support splitting config across modules, but it would still be 'nice' to be able to if solutions can be found, even just in future. Or at least just to try & avoid making decisions that break that use case until necessary. Otherwise we may end up pushing in one direction before we're actually 100% sure about it (as we won't have used any of this in practise for a while).
stevetweeddale
Magic!