This issue will demonstrate what I proposed in #10 of 📌 [policy, then patch] Decide on coding standard for configuration keys of ConfigEntities Active .
TL;DR:
- We want to keep the snake_case config keys, preserving consistency with plain config files
- We want to have camelCase properties on the class, preserving consistency with other classes in the system, and respecting the coding standards.
We can do this with minimum effort by mapping the snake_case config keys to the camelCase properties.
So I suggest having a defined mapping for each config entity, as a part of the annotation.
The mapping would only be used if found, allowing us to fix config entity types one by one.
Needs work
10.1 ✨
Last updated
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
Fixed Failed Commands on #54
Attached patch against Drupal 10.1.x
Attached interdiff
This is a proposal implementing an idea in another issue, 📌 [policy, then patch] Decide on coding standard for configuration keys of ConfigEntities Active . I've just closed that as outdated, so it makes sense to do that to this one as well.