Actually the approach is not that bad and I misunderstood it a bit. The module (in this case this one) is NOT tied to Expressive, as it's actually only the consumer app that needs the dependency to the specific package.
And because the __invoke can be anything, we could quite easily achieve dependencies between modules by making sure the "AppConfig" also aggregates the config of its children.
I'm merging and tagging as 1.1.0 but feel free to tell me if you have any other idea.
danizord
commented
8 years ago
ping @danizord
Actually the approach is not that bad and I misunderstood it a bit. The module (in this case this one) is NOT tied to Expressive, as it's actually only the consumer app that needs the dependency to the specific package.
And because the __invoke can be anything, we could quite easily achieve dependencies between modules by making sure the "AppConfig" also aggregates the config of its children.
I'm merging and tagging as 1.1.0 but feel free to tell me if you have any other idea.