After over a month of concentrated work, Drupal 8 was ready today to finally flip the switch and enforce strict configuration schema adherence in all TestBase derived tests in core. See the announcement in the core group.
If you are a Drupal 8 contrib developer and provided some configuration schema earlier (or you integrate with an existing core system like blocks, views, fields, etc.) then your tests may now fail with configuration schema errors. Unless of course all your configuration schema is correct: #highfive for you then.
Otherwise I thought you'll have questions. There is of course the existing configuration schema documentation that I helped write. However if you are a visual person and want to get an understanding of the basics fast, I thought a cheat sheet would be a great tool. So sat down today and produced this one in the hopes it will help you all! Enjoy!
Please provide feedback for improvements in the comments, and I'll update the sheet as appropriate.
- 1.0: Initial version
- 1.1: Different background colour for schemas for readability; Fixed incorrect [key] and [%parent] examples; some small fixes; thanks Wim Leers
- 1.2: Better wording for parent example labels, clarify naming of internal type vs. top level type; thanks Wim Leers
- 1.3: Fixed config name matching in both examples on second page; fixed 'messages' key matching in last example; minor typos; thanks Michael Prasuhn
- 1.4: Update for simplified sequence format introduced in https://www.drupal.org/node/2414539
- 1.5: Update for new base type for configuration files, config_object, see https://www.drupal.org/node/2460751