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 simpletest module.
Schema in place
Schema not yet in place
simpletest.settings.yml
Comment | File | Size | Author |
---|---|---|---|
#1 | 1919200-simpletest-schema-1.patch | 625 bytes | vijaycs85 |
Comments
Comment #1
vijaycs85Adding schema file...
Comment #3
vijaycs85#1: 1919200-simpletest-schema-1.patch queued for re-testing.
Comment #4
sunI'd like to mark this won't fix for two reasons:
That said, I believe that 1) should be applied as rule of thumb to all modules, regardless of 2). Config schema files should be optional.
Comment #6
Gábor HojtsyRight, I agree config schemas are not required. I don't think we fully explored the use cases for which they will be useful, but this module is not in the immediate use case that we introduced schemas for. I think its fine to mark this won't fix and others who might have use cases can come in and provide those still.