Problem/Motivation

Drupal CMS had to invent this whole-cloth, but in some cases, you might want to be able to get extensive information about a recipe and what it will do.

We already have a dr recipe:info command, but it's very limited. We should also include things like:

  • What modules and themes does this recipe intend to install?
  • What config will it import, and from where?
  • What are the content items it ships?

We should create an API that can glean this information about a recipe, recursively.

Proposed resolution

Add a service that can take a recipe object (or stack of them) and return machine-readable information about them. Expose that information in dr recipe:info.

Remaining tasks

Agree to this, then do it with test coverage.

User interface changes

dr recipe:info may gain some more output.

Introduced terminology

None anticipated.

API changes

Possible API additions.

Data model changes

None.

Release notes snippet

TBD

Comments

phenaproxima created an issue.

nicxvan’s picture

nicxvan commented

Side note, do we need a better api to manage things like this?

function getExtension(string $name): Extension {
    try {
      return $this->moduleList->get($name);
    }
    catch (UnknownExtensionException) {
      return $this->themeList->get($name);
    }
  }