Problem/Motivation
The config/install directories of some modules contain some config with unmet dependencies.
Steps to reproduce
drush si -y minimal
drush en -y l10n_server
-> Configuration objects provided by l10n_server have unmet dependencies: views.view.l10n_server_files (views)
I assume that this is the case in more than just one module.
Proposed resolution
Two options, to be decided per config:
- Move the config to config/optional.
This is only an option if nothing else in the module depends on that configuration.
- Require views (or other) module in the *.info.yml file of the respective module.
Remaining tasks
User interface changes
API changes
Data model changes
Comments
Comment #3
donquixote commentedComment #4
donquixote commentedI am now fixing a lot more stuff in this branch.
Because we can!
Comment #5
donquixote commentedI refactored the integrity test to use iterators.
It's a bit funky but imo it is the way to go.
Comment #6
donquixote commentedI pushed more changes which split the ModuleIntegrityTest.
Now we have a separate test for views, to detect broken handlers.
Maybe we should split things up, and only do the first step here which is about module install.
Comment #7
donquixote commentedI had a look at L10nPackagerDownloadForm which uses that permission.
It seems that form does not really do anything meaningful. It seems like stub code copied from a "how to create a Drupal form" tutorial.
I see that more work is done here, #3338987: Finalize l10n_packager route /downloads..
So maybe we should handle that first.
Comment #20
fmb commented