Problem/Motivation
Configuration should be defined in schema. That's really important for translatable values (though this module doesn't have any now), and it's expected by core - it gives warnings when imported or saved under Drupal 11.
Steps to reproduce
Set up a view with an entity_form_field, save it.
Proposed resolution
Add a schema yml file for views.field.entity_form_field.
| Comment | File | Size | Author |
|---|---|---|---|
| #5 | Screenshot 2026-04-14 at 13.38.45.png | 20.06 KB | travis-bradbury |
| #5 | Screenshot 2026-04-14 at 13.38.27.png | 45.48 KB | travis-bradbury |
| #5 | Screenshot 2026-04-14 at 13.37.10.png | 40.32 KB | travis-bradbury |
| #5 | Screenshot 2026-04-14 at 13.36.50.png | 18.2 KB | travis-bradbury |
Issue fork views_entity_form_field-3559313
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
- 8.x-1.x
changes, plain diff MR !19
- 3559313-define-configuration-schema
compare
Comments
Comment #3
travis-bradbury commentedComment #4
anybodyAbsolutely! Could someone please use https://www.drupal.org/project/config_inspector to review this and add a before / after screenshot?
Then this should get merged!
Comment #5
travis-bradbury commentedHere's the config_inspector results using a simple view of nodes where I added a views_entity_form_field field for the body field.
Before
After
Comment #6
anybody@travis-bradbury if all is fine, could you set this RTBC then?
Comment #7
travis-bradbury commentedComment #10
vladimirausThank you everyone for your contributions.
Committed. 🍻