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 locale module.
Schema in place
Schema not yet in place
locale.settings.yml
| Comment | File | Size | Author |
|---|---|---|---|
| #10 | 1919180-locale-schema-10.patch | 1.55 KB | sandipmkhairnar |
| #10 | 1919180-diff-7-10.txt | 1.55 KB | sandipmkhairnar |
| #10 | lacale-schema-form.png | 46.37 KB | sandipmkhairnar |
| #7 | 1919180-locale-schema-7.patch | 1.58 KB | vijaycs85 |
| #5 | 1919180-locale-schema-5.patch | 1.58 KB | vijaycs85 |
Comments
Comment #1
vijaycs85Adding schema file...
Comment #2
sandipmkhairnar commentedupdating schema as per code style in http://drupal.org/node/1905070#codestyle and verified in config_inspector
Comment #3
vijaycs85Removing existing schema file and minor comment update.
Comment #5
vijaycs85Updating right patch file...
Comment #6
guy_schneerson commented@vijaycs85 Looks great no syntax / Code style issues.
I am not over familiar with all the settings but all but one label look sensible.
The only change I would make is change "Strings cached" to "Cache strings".
Comment #7
vijaycs85Thanks @guy_schneerson. Updated label.
Comment #8
vijaycs85Comment #9
guy_schneerson commentedHi @vijaycs85 thanks for the updated patch.
I have reviewed all the settings and looked at the code implementing them to make sure they describe what they do.
I have located one more issue with the overwrite_customized & overwrite_not_customized.
Those don't match the UI code and don't match the implementation as far as I can see, I actually think the UI code is incorrect and will raise a separate issue.
According to the local PoDatabaseWrite.php
and according to Gettext.php
I think the safest approach is to go with
Comment #10
sandipmkhairnar commentedThanks @guy_schneerson for comments. Updated patch as per comment.
Comment #11
vijaycs85Comment #12
guy_schneerson commentedThanks @vijaycs85 looks good will give it another proper test tomorrow I also posted a related issue Configuration of Import behavior may be unclear / incorect I don't think it directly relates to this patch at the moment as the new labels take a "safe" approach.
Comment #13
guy_schneerson commentedLooks good to me.
We have one potential small issue where all the settings under the "translation" section are all related to the "translation import" but that may be coincidental and other settings may be added to this section in the future.
Comment #14
webchickCommitted to 8.x, thanks! I'll push once testbot has caught up a bit.
Comment #16
rych commentedI've found an item in locale.settings.yml, but it doesn't appear in schema file.
Related issue: Complete Configuration schemas for locale module