Allow config entities to specify the config key <-> entity property mapping

Created on 22 January 2015, almost 10 years ago
Updated 25 January 2023, almost 2 years ago

This issue will demonstrate what I proposed in #10 of #1832630: [policy, then patch] Decide on coding standard for configuration keys of ConfigEntities .

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.

📌 Task
Status

Needs work

Version

10.1

Component
Configuration entity 

Last updated about 5 hours ago

Created by

🇷🇸Serbia bojanz

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

Production build 0.71.5 2024