Name of event fired when missing content dependencies are detected. Events subscribers are fired as part of the configuration import batch. Each subscribe should call \Drupal\Core\Config\MissingContentEvent::resolveMissingContent() when they address a missing dependency. To address large amounts of dependencies subscribers can call \Drupal\Core\Config\MissingContentEvent::stopPropagation() which will stop calling other events and guarantee that the configuration import batch will fire the event

Name of the event fired when importing configuration to target storage. This event allows modules to perform additional actions when configuration is imported. The event listener method receives a \Drupal\Core\Config\ConfigImporterEvent instance. See also \Drupal\Core\Config\ConfigImporterEvent \Drupal\Core\Config\ConfigImporter::import(). \Drupal\Core\EventSubscriber\ConfigSnapshotSubscriber::onConfigImporterImport(). Related topics Events Overview of event dispatch and subscribing File cor

Name of the event fired when deleting a configuration object. This event allows modules to perform an action whenever a configuration object is deleted. The event listener method receives a \Drupal\Core\Config\ConfigCrudEvent instance. See hook_update_N() documentation for safe configuration API usage and restrictions as this event will be fired when configuration is deleted by hook_update_N(). See also \Drupal\Core\Config\ConfigCrudEvent \Drupal\Core\Config\Config::delete() \Drupal\Core\Confi

Name of event fired to collect information on all config collections. This event allows modules to add to the list of configuration collections retrieved by \Drupal\Core\Config\ConfigManager::getConfigCollectionInfo(). The event listener method receives a \Drupal\Core\Config\ConfigCollectionInfo instance. See also \Drupal\Core\Config\ConfigCollectionInfo \Drupal\Core\Config\ConfigManager::getConfigCollectionInfo() \Drupal\Core\Config\ConfigFactoryOverrideBase Related topics Events Overview of

Defines events for the configuration system. Hierarchy class \Drupal\Core\Config\ConfigEvents See also \Drupal\Core\Config\ConfigCrudEvent File core/lib/Drupal/Core/Config/ConfigEvents.php, line 10 Namespace Drupal\Core\Config Members Name Modifiers Type Description ConfigEvents::COLLECTION_INFO constant Name of event fired to collect information on all config collections. ConfigEvents::DELETE constant Name of the event fired when deleting a configuration object

Length limit of the configuration entity prefix. Configuration entity names are composed of two parts: The config prefix, which is returned by getConfigPrefix() and is composed of: The provider module name (limited to 50 characters by DRUPAL_EXTENSION_NAME_MAX_LENGTH). The module-specific namespace identifier, which defaults to the configuration entity type ID. Entity type IDs are limited to 32 characters by EntityTypeInterface::ID_MAX_LENGTH. The configuration entity ID. So, a typical confi

public ConfigEntityTypeInterface::getPropertiesToExport() Gets the config entity properties to export if declared on the annotation. Return value array|null The properties to export or NULL if they can not be determine from the config entity type annotation. File core/lib/Drupal/Core/Config/Entity/ConfigEntityTypeInterface.php, line 72 Class ConfigEntityTypeInterface Provides an interface for a configuration entity type and its metadata. Namespace Drupal\Core\Config\Entity Code public

public ConfigEntityTypeInterface::getLookupKeys() Gets the keys that are available for fast lookup. Return value string[] The list of lookup keys. File core/lib/Drupal/Core/Config/Entity/ConfigEntityTypeInterface.php, line 80 Class ConfigEntityTypeInterface Provides an interface for a configuration entity type and its metadata. Namespace Drupal\Core\Config\Entity Code public function getLookupKeys();

public ConfigEntityTypeInterface::getConfigPrefix() Gets the config prefix used by the configuration entity type. The config prefix is used to prefix configuration entity IDs when they are stored in the configuration system. The default config prefix is constructed from the name of the module that provides the entity type and the ID of the entity type. If a config_prefix annotation is present it will be used in place of the entity type ID. Prefixing with the module that provides the configurati

Provides an interface for a configuration entity type and its metadata. Hierarchy interface \Drupal\Component\Plugin\Definition\PluginDefinitionInterfaceinterface \Drupal\Core\Entity\EntityTypeInterfaceinterface \Drupal\Core\Config\Entity\ConfigEntityTypeInterface File core/lib/Drupal/Core/Config/Entity/ConfigEntityTypeInterface.php, line 10 Namespace Drupal\Core\Config\Entity Members Name Modifiers Type Description ConfigEntityTypeInterface::getConfigPrefix public funct