Early Bird Registration for DrupalCon Portland 2024 is open! Register by 23:59 UTC on 18 March 2024, to get $100 off your ticket.
Problem/Motivation
See https://www.drupal.org/core/experimental#beta
- We will be API stable - all main API classes will have @internal removed
- Config Transformation event API will have been moved to core
Proposed resolution
Ensure we're ready for the beta gates - ie. API stability, deprecations and upgrade paths.
Comments
Comment #2
alexpottComment #3
alexpottComment #4
xjmWe shouldn't be moving anything into core namespaces until the module is being marked stable, unless the functionality would be added even without the experimental module existing. Otherwise, it's beta code in a stable namespace.
Comment #5
bircherI absolutely agree with #4.
We are in the second case with #2991683: Move configuration transformation API in \Drupal\Core\Config namespace and #3079029: Move module config exclusion from config_environment to core.services:
While we are still working on the config_environment module and what was planned for it, in the mean time we used it to solve the chicken-egg problem with having the api without using it. Since we now have a use for the API in core outside of the config_environment module, the API can go into core also without the experimental module.
We can remove
@internal
from\Drupal\Core\Config\ImportStorageTransformer
which is the only API class one is expected to use.Ie
\Drupal::service('config.import_transformer')->transform($myStorage);
The other direction is covered by
\Drupal\Core\Config\StorageInterface
when using theconfig.storage.export
service.Comment #7
bircher