Autoremove --dry-run type concept?

[chrisdavidmiles]

Standardizing plugin dependencies sounds great for developers and for end users. I'm also wondering about this problem but in the other direction.

For instance: If a plugin A is in use on a site only because plugin B had unmet dependencies, if plugin B gets uninstalled, and there is no longer any dependency on plugin A, is that information the user might benefit from in /wp-admin/ ? And if so, would it be helpful to surface that information? (particularly if/when themes start to make use of this). Think of all the sites still using "titan framework" who no longer need to only because another plugin used to require it.

Is there any interest in an autoclean --dry-run type concept, similar to what's available in apt / yum / brew ? Perhaps only informational?

Or would storing/surfacing that information only be unnecessary complexity, given there are no plans for plugin dependencies to automatically install/activate?

Thoughts?

[afragen]

Sounds like a good idea for a second stage of the project.