Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.This was split off from #2224761-145: Add a generic way to add third party configuration on configuration entities and implement for field configuration
Problem/Motivation
Our coding standards say that all class properties must be named using camelcase. However, we don't always do this, especially when properties are dynamically mapped to other data structures that either forbid camelcasing, or where we just never use it.
The problem is basically that we ignore low-level coding standards to solve more high-level naming issues that are caused by lack of mapping functionality between two systems that use different standards, whether those standards are officially documented or are just a convention.
Proposed resolution
T.B.D.
Remaining tasks
T.B.D.
User interface changes
None.
API changes
T.B.D.
Comments
Comment #1
XanoI propose the following solution:
Comment #2
Gábor HojtsyI don't think this is worth the DX pain of the mapping system.
Comment #3
XanoWhat about the DX pain of breaking coding standards, or of even having inconsistent standards at all?
Comment #4
xjmThe parts of this that touch the entity and config systems at least are beta deadline, so tagging as such.
I think this is more task than bug. Thanks @Xano!
Comment #5
xjmForgot a tag.
Comment #6
XanoBump, because fixing this may break a few minor things.
Comment #7
bojanz CreditAttribution: bojanz commentedLet's just use camelCase in YAML files, and we're good, no need for mapping.
Comment #8
XanoComment #16
xjmComment #21
quietone CreditAttribution: quietone at PreviousNext commentedThis is being addressed in #2937514: Fix Drupal.NamingConventions.ValidVariableName.LowerCamelName in tests.
If you disagree with the current Coding standards proposals can be made in the Coding Standards Project.