search

computerminds / cm_config_tools

DEPRECATED: Mirror of http://cgit.drupalcode.org/cm_config_tools
1 stars 0 forks source link

Minimise dependencies #5

Closed anotherjames closed 7 years ago

anotherjames commented 8 years ago

If module A is dependent on module B ... then if we're listing module A as a dependency, we don't really need to list module B.

anotherjames commented 7 years ago

...for that scenario, it may be considered true that any config in module B's /config/install could also then be considered 'installed' and would not need to be brought in as an implicit dependency either.

Anyway, so module dependencies should be checked recursively too, including the module dependencies listed in their .info.yml file(s), which we don't currently do anywhere.

anotherjames commented 7 years ago

I don't think we can assume an external module's config from /config/install will be around. Eg. Core's thumbnail image style could have been edited (to change its dependencies) or deleted (as part of a pro-active client's overzealous spring cleaning?). But we can assume config from other cm_config_tools modules (though only those that are dependencies) is around. unless they're marked unmanaged, as they could have different dependencies (though they will at least exist).

anotherjames commented 7 years ago

This is basically done now in f5241907a5e76464259d27788602f1130a12d0f0.