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 the idea of config schema. 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
Create a configuration schema for rest module.
Schema in place
Schema not yet in place
rest.settings
Comment | File | Size | Author |
---|---|---|---|
#4 | REST Config.jpg | 131.17 KB | rajeevk |
#2 | 2107687-rest-config-schema-2.patch | 1.26 KB | vijaycs85 |
#2 | rest.settings.png | 80.04 KB | vijaycs85 |
#2 | rest-config.png | 109.86 KB | vijaycs85 |
Comments
Comment #1
vijaycs85Comment #2
vijaycs85Initial patch with test config to make sure it is working in config_inspector.
Comment #3
klausiSo we were talking about something like this regarding #2065193: supported_formats and supported_auth should work in the same way. Do we get validation capabilities with this? If the rest.settings.yml file is misformatted will the config import fail? Can we then later assume that the config is always in the correct format and we don't have to watchdog() ourselves?
Comment #3.0
klausiUpdated issue summary.
Comment #4
rajeevkApplied the patch & checked manualy. It works perfectly, screenshot attached.
Changing status to RTBC.
Comment #5
Xano2: 2107687-rest-config-schema-2.patch queued for re-testing.
Comment #6
webchickCommitted and pushed to 8.x. Thanks!