Managing newly created module dependencies on fly

[bartoszkubicki]

That's enhancement I would find useful, but don't know the architecture of your library for now, so just posting an idea.

So, let's assume we generate certain types of templates, with an option of module creation on the fly. It would be nice to have dependencies sorted out in process. For example, generation of crontab, should be followed by adding dependency to Magento_Cron in module.xml and composer.json. However there are some issues I see:

• it is possible only if we say 'yes' to question if we would like to have module generated - I assume we should get that question every time we generate something
• it is a problem to resolve package version (for composer version) if we don't know for which magento version code is generated - it can be avoided by putting wildcard (*) on the other hand or we could specify our target magento version in some config file
• matrix of dependencies vs template has to be stored in some config file, but I don't know if there are templates that can generate code dependant to different packages according to what we insert during survey in CLI

[michalbiarda]

Thanks for the suggestion. It should be easy to add it for module.xml, but as you mentioned, might be tricky/impossible for composer.json. I'll think about it. Maybe it could be just added as "after generation" suggestion.