Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow configuration of installed modules for inspection #4

Open
mglaman opened this issue Dec 19, 2018 · 3 comments
Open

Allow configuration of installed modules for inspection #4

mglaman opened this issue Dec 19, 2018 · 3 comments
Labels
enhancement New feature or request

Comments

@mglaman
Copy link
Owner

mglaman commented Dec 19, 2018

Currently, this extension loads all available modules. In reality, we should be allowed to limit the scope of this.

This would require moving the bootstrap process into the container somehow, so the list of modules can be provided as a parameter. If its empty we can assume "all of the things."

@mglaman
Copy link
Owner Author

mglaman commented Dec 20, 2018

This is harder than it seems. The Extension class has no method of tracking dependencies.

It is actually parsed in \Drupal\Core\Extension\ModuleExtensionList::doList. Somehow, somewhere the extension has a magical info property info, which is the parsed YAML.

Then in \Drupal\Core\Extension\ModuleHandler::buildModuleDependencies the dependencies are discovered.

@mglaman mglaman added the enhancement New feature or request label Dec 20, 2018
@morsok
Copy link

morsok commented Jan 9, 2019

Without this feature bugs in core like this one https://www.drupal.org/project/drupal/issues/3020142 causes an error, with this feature the modules won't be loaded :)

@mglaman
Copy link
Owner Author

mglaman commented Feb 24, 2022

This can be achieved with #343.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants