This is a sub-issue of #1910624: [META] Introduce and complete configuration schemas in all of core.


#1866610: Introduce Kwalify-inspired schema format for configuration introduced some config schema coverage for views, but it is not complete. The changelog leads to (hopefully extensive) documentation on the format at While there are little cleanups planned for the format overall, the current format is a result of months of back and forths, so it should be perfectly fine to apply it more widely to core.

Proposed solution

Figure out the missing pieces that are not yet covered. Write schema file sections for them. Clean up / fix any issues in current schema.

Create a configuration schema for view components access, area, argument, argument_default, argument_validator, cache, display, display_extender, exposed_form, field, filter, handler, pager, sort, style (whichever applicable) in user module.

Schema in place

Schema not yet in place



Add additional parts of identified schemas.

Steps to review

Check Steps to check on meta.

#1 1991260-views-config-schema-user-1.patch1.04 KBvijaycs85
PASSED: [[SimpleTest]]: [MySQL] 59,516 pass(es). View
Members fund testing for the Drupal project. Drupal Association Learn more


vijaycs85’s picture

Status: Active » Needs review
1.04 KB
PASSED: [[SimpleTest]]: [MySQL] 59,516 pass(es). View

Initial patch...

dawehner’s picture

Do you have an oppinion whether all of the schema should be put into this issue. There are potentially a lot of different views plugins.

vijaycs85’s picture

@dawehner, we can try sub-issue, if we have a lot. I will users module and update this issue or create new one.

dawehner’s picture

I agree, whatever works.

vijaycs85’s picture

Issue summary: View changes

Updated issue summary.

dawehner’s picture

dawehner’s picture

Issue summary: View changes

RTBC, as long the retest agrees as well.

ianthomas_uk’s picture

Status: Needs review » Reviewed & tested by the community

The retest agreed, so RTBC by dawehner

webchick’s picture

Status: Reviewed & tested by the community » Fixed

Committed and pushed to 8.x. Thanks!

Status: Fixed » Closed (fixed)

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