Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.Problem/Motivation
When an extra field with settings is configured, it does not comply with the configuration schema of Drupal.
Steps to reproduce
- Install the Extra Field Settings Provider Example module.
- Install the Configuration Inspector module.
- Go to admin/structure/types/manage/page/display.
- Place Example Node Label to the Content region.
- Click on the settings icon next to the Example Node Label, and save the display settings as-is.
- Go to admin/reports/config-inspector.
- The core.entity_view_display.node.page.default config contains errors.
- The content.extra_field_example_node_label.settings.wrapper has a missing schema.
- The content.extra_field_example_node_label.settings.link_to_entity has a missing schema.
Proposed resolution
Add a 'type' config key to the extra fields, so a config schema for these extra fields can be created.
Remaining tasks
Create patch with proposed resolution.
User interface changes
None.
API changes
Only additions - it is now also possible to create a config schema for the settings of extra fields, but it doesn't change anything for fields that don't have one yet.
Data model changes
None.
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | Screenshot 2022-05-04 162655.png | 79.89 KB | bartlangelaan |
| #2 | 3278684-2.patch | 1.19 KB | bartlangelaan |
| Screenshot 2022-05-04 160419.png | 79.53 KB | bartlangelaan |
Comments
Comment #2
bartlangelaanSee attached patch.
See also the screenshot for the changed result.
Comment #3
grevil commentedJust tested the patch through #3270794: Write tests for basic functionality! Without this patch, the tests would throw schema errors, with this patch applied the schema errors were gone and the view_display could be created correct and successfully!
Comment #4
anybodyComment #5
anybody