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 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
views.argument_default.user
views.argument_default.current_user
views.argument_validator.user
Add additional parts of identified schemas.
Steps to review
Check Steps to check on meta.
Comment | File | Size | Author |
---|---|---|---|
#1 | 1991260-views-config-schema-user-1.patch | 1.04 KB | vijaycs85 |
Comments
Comment #1
vijaycs85Initial patch...
Comment #2
dawehnerDo you have an oppinion whether all of the schema should be put into this issue. There are potentially a lot of different views plugins.
Comment #3
vijaycs85@dawehner, we can try sub-issue, if we have a lot. I will users module and update this issue or create new one.
Comment #4
dawehnerI agree, whatever works.
Comment #4.0
vijaycs85Updated issue summary.
Comment #5
dawehner1: 1991260-views-config-schema-user-1.patch queued for re-testing.
Comment #6
dawehnerRTBC, as long the retest agrees as well.
Comment #7
ianthomas_ukThe retest agreed, so RTBC by dawehner
Comment #8
webchickCommitted and pushed to 8.x. Thanks!