Unify name property of configuration entities.

Created on 29 May 2014, about 11 years ago
Updated 23 June 2025, about 11 hours ago

Problem/Motivation

As mentioned by @Gábor Hojtsy in #2273631-8: Unify config entity schemas with a base schema type → the name property of config entities used for two different purpose on different entities. 1) as a machine name. 2) As a name/label (human readable name). This become problem when try to unify this field as part of common data_type.

Proposed resolution

1. Use 'name' for one specific purpose (either machine name or label) and introduce new field where necessary.

Remaining tasks

Discuss
patch

User interface changes

N/A

API changes

N/A

📌 Task
Status

Postponed: needs info

Version

11.0 🔥

Component

configuration entity system

Created by

🇬🇧United Kingdom vijaycs85 London, UK

Live updates comments and jobs are added and updated live.
  • D8MI

    (Drupal 8 Multilingual Initiative) is the tag used by the multilingual initiative to mark core issues (and some contributed module issues). For versions other than Drupal 8, use the i18n (Internationalization) tag on issues which involve or affect multilingual / multinational support. That is preferred over Translation.

  • stale-issue-cleanup

    To track issues in the developing policy for closing stale issues, [Policy, no patch] closing older issues

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.

  • 🇺🇸United States smustgrave

    Thank you for creating this issue to improve Drupal.

    We are working to decide if this task is still relevant to a currently supported version of Drupal. There hasn't been any discussion here for over 8 years which suggests that this has either been implemented or is no longer relevant. Your thoughts on this will allow a decision to be made.

    Since we need more information to move forward with this issue, the status is now Postponed (maintainer needs more info). If we don't receive additional information to help with the issue, it may be closed after three months.

    Thanks!

Production build 0.71.5 2024