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 translation module.

Schema in place

Schema not yet in place
translation.settings.yml

Files: 
CommentFileSizeAuthor
#2 1919216-translation-schema-2.patch503 bytesvijaycs85
PASSED: [[SimpleTest]]: [MySQL] 52,206 pass(es). View
#1 1919216-translation-schema-1.patch406 bytesvijaycs85
PASSED: [[SimpleTest]]: [MySQL] 50,989 pass(es). View

Comments

vijaycs85’s picture

Status: Active » Needs review
FileSize
406 bytes
PASSED: [[SimpleTest]]: [MySQL] 50,989 pass(es). View

Adding schema file...

vijaycs85’s picture

FileSize
503 bytes
PASSED: [[SimpleTest]]: [MySQL] 52,206 pass(es). View

Updated code style and verified with config_inspector

pfrenssen’s picture

Assigned: Unassigned » pfrenssen

Assigning for review.

pfrenssen’s picture

Assigned: pfrenssen » Unassigned
Status: Needs review » Reviewed & tested by the community

Looks great, RTBC!

webchick’s picture

Status: Reviewed & tested by the community » Fixed

Committed and pushed to 8.x. Thanks!

Automatically closed -- issue fixed for 2 weeks with no activity.