You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jun 15, 2026. It is now read-only.
Repository navigation
This repository was archived by the owner on Jun 15, 2026. It is now read-only.
Add ability to define dependencies in composition templates #164
Not sure how easy, or what the consequences would be, but it would make authoring templates that have slight variations for different (MVVM) frameworks if it was possible to specify a dependency in a composition template.
Had a look into this and to support this, we'd have to change a few things:
Change the way the generation queue is built. Currently it resolves dependencies first, and then adds in compositions for each template.
Change how dependencies are resolved. Currently dependencies are defined by identity, to support dependencies on compositions we should define dependencies by groupIdentity
This would also require changes in the wizard, we'd have to inspect compositions of a template to be able to show all dependencies.
Don't think this is a priority right now, also not sure if the benefit this brings justifies the complexity this adds to the system.
I understand that this is a complex change of low priority and I'm happy for it to sit on the backlog until there's a stronger argument for doing this work.
Activity
sibille commentedon Jul 12, 2019
Had a look into this and to support this, we'd have to change a few things:
Don't think this is a priority right now, also not sure if the benefit this brings justifies the complexity this adds to the system.
mrlacey commentedon Jul 12, 2019
I understand that this is a complex change of low priority and I'm happy for it to sit on the backlog until there's a stronger argument for doing this work.