At the moment it is possible to create config entity types than have config prefixes that do not start with the name of the module that provides the entity. This is bad news for default configuration installation and configuration dependency management. Neither or which will work as expected.
- Ensure that the value returned by EntityType::getConfigPrefix() starts with the provider
- If the config entity does not have a config_prefix annotation concatenate the provider and the entity type ID
- If a config_prefix is supplied this is concatenated with the provider.
- Depends on
- Write patch
User interface changes