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

Problem/motivation

#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 http://drupal.org/node/1905070. 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 entity type entity_form_display.

Files: 
CommentFileSizeAuthor
#1 2096367-entity-form-display-1.patch12.25 KBvijaycs85
PASSED: [[SimpleTest]]: [MySQL] 58,616 pass(es). View

Comments

vijaycs85’s picture

Status: Active » Needs review
FileSize
12.25 KB
PASSED: [[SimpleTest]]: [MySQL] 58,616 pass(es). View

Initial patch...

vijaycs85’s picture

Issue summary: View changes
Status: Needs review » Closed (duplicate)
Related issues: +#2167623: Add test for all default configuration to ensure schema exists and is correct

The patch on this issue has been updated as part of #2167623: Add test for all default configuration to ensure schema exists and is correct. As this issue doesn't have any test to confirm/validate the schema, making this change and closing this issue as duplicate of #2167623: Add test for all default configuration to ensure schema exists and is correct. The contributors of this issue (in commit message) is copied to #2167623: Add test for all default configuration to ensure schema exists and is correct.