public function ConfigDevelCommands::__construct in Configuration development 8

Constructs a new ConfigDevelCommands object.

Parameters

\Drupal\Core\Extension\ModuleHandlerInterface $moduleHandler: The module handler.

\Drupal\Core\Extension\ThemeHandlerInterface $themeHandler: The theme handler.

\Drupal\Core\Extension\InfoParserInterface $infoParser: The parser for info.yml files.

\Drupal\Core\Config\ConfigFactoryInterface $configFactory: The configuration object factory.

\Drupal\config_devel\ConfigImporterExporter $autoExportSubscriber: The event subscriber that listens to config change events, and happens to contain some code that we depend on which should be factored out into a separate service.

\Drupal\config_devel\EventSubscriber\ConfigDevelAutoImportSubscriber $autoImportSubscriber: The event subscriber that listens to config change events, and happens to contain some code that we depend on which should be factored out into a separate service.

\Drupal\Core\File\FileSystemInterface $fileSystem: The file system service.

File

src/Commands/ConfigDevelCommands.php, line 91

Class

ConfigDevelCommands

Drush integration for the Configuration Development module.

Namespace

Drupal\config_devel\Commands

Code

public function __construct(ModuleHandlerInterface $moduleHandler, ThemeHandlerInterface $themeHandler, InfoParserInterface $infoParser, ConfigFactoryInterface $configFactory, ConfigImporterExporter $config_import_export, ConfigDevelAutoImportSubscriber $autoImportSubscriber, FileSystemInterface $fileSystem) {
  parent::__construct();
  $this->moduleHandler = $moduleHandler;
  $this->themeHandler = $themeHandler;
  $this->infoParser = $infoParser;
  $this->configFactory = $configFactory;
  $this->configImportExport = $config_import_export;

  // @todo We should not depend on event subscribers directly.
  // @see https://www.drupal.org/node/2388253
  $this->autoImportSubscriber = $autoImportSubscriber;
  $this->fileSystem = $fileSystem;
}