Problem/Motivation

I think as a result of changes in core (citation/issue link needed), field storage is no longer a separate form. In practice, this means that we don't directly expose a config enforce UI from within the Field UI forms.

Steps to reproduce

Add/edit a field through Field UI.

We would expect to see field and field.storage configs that can be enforced, but are only seeing the field instance config.

Proposed resolution

Handle this in ConfigResolver as a special case.

Remaining tasks

Test this with Drupal 10 (assuming the UI was changed in D11) to make sure we don't add duplicate UI elements there or similar.

User interface changes

API changes

Data model changes

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

star-szr created an issue. See original summary.

star-szr’s picture

Issue summary: View changes

star-szr’s picture

Status: Active » Needs review

  • star-szr committed 7b9cf7ff on 2.0.x
    docs: #3557764 Add TODO for test coverage
    
    By: @ergonlogic
    By: @star-szr
    

  • star-szr committed 6977a493 on 2.0.x
    fix: #3557764 Handle Field UI forms which contain both field instance...
star-szr’s picture

Status: Needs review » Fixed

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.

  • star-szr committed a72cd164 on 2.0.x
    test: #3557764 Add coverage for display of field storage config
    

  • star-szr committed 14f92422 on 2.0.x
    test: #3557764 Add field to config_enforce_node_test
    

  • star-szr committed 0405e1f3 on 2.0.x
    test: #3557764 Fix config_enforce_node_test registry name
    
star-szr’s picture

Issue tags: -Needs tests

Status: Fixed » Closed (fixed)

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