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

Comments

tim.plunkett’s picture

Version: 8.0.x-dev » 8.1.x-dev

Here are the core config entities that use something other than id for their ID key:

  • \Drupal\filter\Entity\FilterFormat::$format
  • \Drupal\image\Entity\ImageStyle::$name
  • \Drupal\node\Entity\NodeType::$type
  • \Drupal\taxonomy\Entity\Vocabulary::$vid

These are the ones using something other than label for their label key:

  • \Drupal\field\Entity\FieldStorageConfig::$id (this is also it's ID key)
  • \Drupal\filter\Entity\FilterFormat::$name
  • \Drupal\node\Entity\NodeType::$name
  • \Drupal\taxonomy\Entity\Vocabulary::$name

So FilterFormat, ImageStyle, NodeType, and Vocabulary (the FieldStorageConfig is purposeful).

These are all protected properties, and in theory we could upgrade config files. It wouldn't help stuff in /config/install for modules...

Version: 8.1.x-dev » 8.2.x-dev

Drupal 8.1.0-beta1 was released on March 2, 2016, which means new developments and disruptive changes should now be targeted against the 8.2.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.2.x-dev » 8.3.x-dev

Drupal 8.2.0-beta1 was released on August 3, 2016, which means new developments and disruptive changes should now be targeted against the 8.3.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.3.x-dev » 8.4.x-dev

Drupal 8.3.0-alpha1 will be released the week of January 30, 2017, which means new developments and disruptive changes should now be targeted against the 8.4.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.