Contrib.social

Installed as a dependency module status

Open on Drupal.org →
Created on 12 July 2024, about 2 months ago
Updated 15 July 2024, about 2 months ago

Problem/Motivation

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.

✨ Feature request
Status

Needs work

Version

11.0 🔥

Component
System  →

Last updated 1 day ago

No maintainer
Created by

🇦🇺Australia nterbogt

Live updates comments and jobs are added and updated live.
  • Needs issue summary update

    Issue summaries save everyone time if they are kept up-to-date. See Update issue summary task instructions.

  • Needs framework manager review

    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.

  • Needs tests

    The change is currently missing an automated test that fails when run with the original code, and succeeds when the bug has been fixed.

Sign in to follow issues

Comments & Activities

contrib.social Blog FAQ Discussions
Production build 0.71.5 2024