Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.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 file module.
Schema in place
Schema not yet in place
file.settings.yml
| Comment | File | Size | Author |
|---|---|---|---|
| #6 | comparison-file.png | 567.92 KB | YesCT |
| #4 | 1919166-file-schema-4.patch | 728 bytes | vijaycs85 |
| #2 | 1919166-file-schema-2.patch | 727 bytes | vijaycs85 |
| #2 | 1919166-diff-1-2.txt | 1.25 KB | vijaycs85 |
| #1 | 1919166-file-schema.patch | 545 bytes | vijaycs85 |
Comments
Comment #1
vijaycs85Adding schema file...
Comment #2
vijaycs85Updating patch with code style from http://drupal.org/node/1905070#codestyle.
Comment #4
vijaycs85Label fix...
Comment #5
vijaycs85Comment #6
YesCT CreditAttribution: YesCT commentedThe schema file meets the standards in http://drupal.org/node/1905070#codestyle , looks good.
I did a manual visual comparison between the schema and the data yml, looks good.
I could not find where a form might be in the UI for description and icon, so did my best guess, which was to add a file field to a content type and then create that content.
So. rtbc.
--
only small thing I noticed was an extra blank like in the file.settings.yml
Comment #7
webchickCommitted and pushed to 8.x. Thanks!