search

computerminds / cm_config_tools

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

Drush command to get dependencies #3

Closed anotherjames closed 7 years ago

anotherjames commented 8 years ago

I'm not sure we actually need this, but we could have a drush command to list dependencies ... either of a specific extension, or all extensions. It would call \Drupal::service('cm_config_tools')->getExtensionConfigDependencies() and/or \Drupal::service('cm_config_tools')->getConfigDependencies().

But realistically, I'm not sure why we'd ever actually invoke this on its own? The export drush command goes straight to the export method which itself just makes a simple call to the getExtensionConfigDependencies method during its execution, it simply doesn't need to be a chain of simpler [drush] commands.

If anything, maybe the exportExtensionDirectories method could be split up so a subroutine could be factored out to actually write a list of known config to a directory, if we really want to split things up and make them simpler for chaining together. But personally I think that's overkill.

Anyway, I've written this up.

anotherjames commented 7 years ago

This probably isn't necessary, but that should be reviewed as part of the implicit-dependencies MVP cycle.

anotherjames commented 7 years ago

I'm honestly not sure why this would still be needed. I suspect it was confused with the need for #25, i.e. suggesting config to export.