Test automatically including module dependencies

I absolutely think it is the correct behavior. We cannot, and should not, expect recipe authors to dig all the way through the extensions' dependency trees to list everything explicitly - besides, the dependencies may change without warning. This would also be a major DX improvement for recipe authoring. They should only list what they want -- the fact that those extensions have dependencies is a detail that should not be relevant to recipe authors.

So +1000 for this.

Note we do this at the moment... see

    foreach ($modules as $module) {
      if ($module_data[$module]->requires) {
        $modules = array_merge($modules, array_keys($module_data[$module]->requires));
      }
    }

in \Drupal\Core\Recipe\InstallConfigurator::__construct()

I think this issue should remove the @todo and add test coverage

Wrote explicit test coverage for InstallConfigurator, and removed the todo along with all the redundant dependencies listed in the Standard recipe suite.

Committed and pushed 8af7fa958bf to 11.x and be3780bbcb2 to 10.3.x. Thanks!

Pushed to the core MR too.

Automatically closed - issue fixed for 2 weeks with no activity.