As a maintainer of a large site, I'd like to have three module status' be available. Apart from the 'installed' status and 'uninstalled' status... I'd like a third status so that I know if a module was installed as a dependency (and not directly installed).
This would allow me to uninstall a module when a feature is no longer required and then assess any modules that were automatically enabled as to whether they are still required.
This would mean I could maintain a faster, more secure, site with less maintenance overheads.
Would also assist maintainers understand sites that weren't necessarily developed by them.
Needs work
11.0 🔥
Issue summaries save everyone time if they are kept up-to-date. See Update issue summary task instructions.
It is used to alert the framework manager core committer(s) that an issue significantly impacts (or has the potential to impact) multiple subsystems or represents a significant change or addition in architecture or public APIs, and their signoff is needed (see the governance policy draft for more information). If an issue significantly impacts only one subsystem, use Needs subsystem maintainer review instead, and make sure the issue component is set to the correct subsystem.
The change is currently missing an automated test that fails when run with the original code, and succeeds when the bug has been fixed.
I have created a custom module for this requirement and push code 3460930-installed-as-a on this branch
Issue summary is incomplete, should be using standard template
Don't see anything to review but adding a tab would most likely require framework manager approval
Will definitely need test coverage.