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 picture module.
Schema in place
Schema not yet in place
picture.schema.yml
| Comment | File | Size | Author |
|---|---|---|---|
| #1 | 1964592-picture-schema-1.patch | 989 bytes | vijaycs85 |
Comments
Comment #1
vijaycs85Updating patch...
Comment #2
attiks commentedSince this is pretty new to me, some comments
I assume status is added to all config entities?
Is the language mandatory, I can not think of a use case where we need a different mapping depending on the language.
Comment #3
gábor hojtsyStatus is indeed a built-in part of config entities. Unless you define a custom export key list, it will be exported into .yml. See http://api.drupal.org/api/drupal/core%21lib%21Drupal%21Core%21Config%21E...
The language does not indicate a language variance of the mapping. It indicates the language the mapping was saved in. Since the mapping has a label (which is human facing I assume), the language of the mapping is the language of the human facing textual pieces of it. langcode is a built-in feature of all config entities. Config entities used to be saved with 'und' prior to earlier today, as of #1947814: New config entities often save as langcode: und incorrectly.
Comment #4
attiks commented#3 Thanks for the clarification!
Comment #5
webchickCommitted and pushed to 8.x. Thanks!
Comment #6
webchickAlso?
Holy confusing, Batman. :)
Comment #7
vijaycs85LOL, yeah... Thank god it's not 'mapping' :)
Comment #9
eli-t