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 the idea of config schema. 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

Create a configuration schema for rest module.

Schema in place

Schema not yet in place

#4 REST Config.jpg131.17 KBRajeevK
#2 2107687-rest-config-schema-2.patch1.26 KBvijaycs85
PASSED: [[SimpleTest]]: [MySQL] 60,352 pass(es). View
#2 rest.settings.png80.04 KBvijaycs85
#2 rest-config.png109.86 KBvijaycs85
Members fund testing for the Drupal project. Drupal Association Learn more


vijaycs85’s picture

Title: Provide configuration Rest for Simpletest module » Provide configuration schema for Rest module
vijaycs85’s picture

Status: Active » Needs review
109.86 KB
80.04 KB
1.26 KB
PASSED: [[SimpleTest]]: [MySQL] 60,352 pass(es). View

Initial patch with test config to make sure it is working in config_inspector.

klausi’s picture

So 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?

klausi’s picture

Issue summary: View changes

Updated issue summary.

RajeevK’s picture

Issue summary: View changes
Status: Needs review » Reviewed & tested by the community
131.17 KB

Applied the patch & checked manualy. It works perfectly, screenshot attached.

Changing status to RTBC.

Xano’s picture

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.