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.

Command icon 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:

Comments

travis-bradbury created an issue. See original summary.

travis-bradbury’s picture

Status: Active » Needs review
anybody’s picture

Issue tags: +Novice

Absolutely! 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!

travis-bradbury’s picture

Here'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

config inspector list shows 1 error for the view

 missing schema

After

config inspector list shows "Correct"

Config inspector details shows no error

anybody’s picture

@travis-bradbury if all is fine, could you set this RTBC then?

travis-bradbury’s picture

Status: Needs review » Reviewed & tested by the community

vladimiraus made their first commit to this issue’s fork.

vladimiraus changed the visibility of the branch 3559313-define-configuration-schema to hidden.

vladimiraus’s picture

Issue summary: View changes
Status: Reviewed & tested by the community » Fixed

Thank you everyone for your contributions.
Committed. 🍻

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.