- 🇮🇹Italy kopeboy Milan
I second catch, regardeless of the version, knowing which other modules are related is useful, both dependants and required (on which the module depends).
When looking at modules, one of the metrics to know about quality is how many depend on that module. Also this is a great way to discover modules that extend the functionality of that module. It would be really great if we could that dependency information on project pages.
There are multiple reasons i'm asking for this:
The reason I ran into this was also because of the d10readiness initiative. We need to test projects that depend on core modules that are getting removed. To find good candidates for these tests this information would be VERY helpful.
Eh.
I would propose something modeled after packagist:
packagist.org/packages/drupal/core-recommended/dependents
New link on the project pages to list dependends of that project.
None.
None hopfully, this information should already be available somewhere.
Active
3.0
Code
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
I second catch, regardeless of the version, knowing which other modules are related is useful, both dependants and required (on which the module depends).