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 has been archived by the owner on May 1, 2019. It is now read-only.
Can't we just use the require and suggest sections of composer.json?
I think:
Modules should register related/optional/child modules/plugins in the suggest section of composer.json.
Plugin/extension/child modules should probably list parent modules in the require section of composer.json.
This would make it easier for developers to publish modules with dependencies (information about related modules), without having to set related modules on the website, relations will be identified by analyzing composer.json files of dependencies listed in sections require/suggest of the main composer.json. This could work, but has one requirement: we need to be able to identify zf-modules among other dependencies listed in require/suggest.
And at this point #159 may become useful. Maybe we could identify zf-modules by a keyword or by the type in composer.json, as described in #159.
Perhaps even a simple 'related modules' feature would be adequate.
(This would be low priority -- just putting it here as a reminder.)
The text was updated successfully, but these errors were encountered: