Now that the config schema fallback has been removed from Drupal 9 we can improve how the 'config_export' annotation property is handled.
In Drupal 9 it required in order to export a configuration entity - this makes it basically always required - so we should change it to be. We should throw an earlier exception that the one thrown in \Drupal\Core\Config\Entity\ConfigEntityBase::toArray() - maybe we can do something in discovery.
Also the \Drupal\Core\Config\Entity\ConfigEntityType::getPropertiesToExport() no longer needs the ID argument at all so we should deprecate that.
Plus once $this->config_export is required the logic can be made simpler.
Active
11.0 🔥
Last updated
Changes an existing API or subsystem. Not backportable to earlier major versions, unless absolutely required to fix a critical bug.
A change record needs to be drafted before an issue is committed. Note: Change records used to be called change notifications.
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
Ran into this while working on 🐛 Require `langcode: …` only for simple config that contains translatable values Active
It's not clear to me what the relationship between this and #2949021: Deprecate schema fallback in ConfigEntityType::getPropertiesToExport → is. Ah, no it was made recommended there 😬