Coming from #2094499-30: Convert "Manage (form) display" forms to be the official entity edit forms for EntityView[Form]Display objects

Not sure if that is a bug or an intended behavior, but this feels a bit weird.

The config schema for core.entity_view_display.*.*.* incorrectly lists a 'label' property, that doesn't actually exist on EntityViewDisplay objects.
As a result, core.entity_view_display.*.yml files contain a 'label: null' entry, meaning ConfigEntity::toArray() force-adds entries with a NULL value for properties found in the schema but not in the object.

It seems that this is only true for the top-level properties: for a mapping nested within an inner porperty, the schema might describe entries that are not always present, and those won't result in null entries added in the nested entry in the yaml (which is a good thing IMO ?).

The difference in behavior between top-level and nested mappings feels wrong ?

Comments

yched’s picture

Title: Entries present at the top-level of the config schema but absent from runtimle ConfigEntities appear as 'null' in the YAML » Entries present at the top-level of the config schema but absent from runtime ConfigEntities appear as 'null' in the YAML

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

Drupal 8.0.6 was released on April 6 and is the final bugfix release for the Drupal 8.0.x series. Drupal 8.0.x will not receive any further development aside from security fixes. Drupal 8.1.0-rc1 is now available and sites should prepare to update to 8.1.0.

Bug reports should be targeted against the 8.1.x-dev branch from now on, and new development or disruptive changes should 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.1.x-dev » 8.2.x-dev

Drupal 8.1.9 was released on September 7 and is the final bugfix release for the Drupal 8.1.x series. Drupal 8.1.x will not receive any further development aside from security fixes. Drupal 8.2.0-rc1 is now available and sites should prepare to upgrade to 8.2.0.

Bug reports should be targeted against the 8.2.x-dev branch from now on, and new development or disruptive changes should 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.2.x-dev » 8.3.x-dev

Drupal 8.2.6 was released on February 1, 2017 and is the final full bugfix release for the Drupal 8.2.x series. Drupal 8.2.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.3.0 on April 5, 2017. (Drupal 8.3.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.3.x-dev branch from now on, and new development or disruptive changes should 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.