3. It will open up some more options, like tracking configuration names for strings belonging to configuration, which is needed for this (next step),
And overall, we are building a cleaner/healthier Locale Storage API, mainly aiming at translating hardcoded configuration strings (yml files), but also helping other efforts like a more reliable and cleaner string translation during install, upgrades, etc... Related:
... which eventually will allow us to fix the way the whole locale system is initialized using DIC...
There are a lot of cirtular dependencies between these other issues so this looks like a good first step to clean up what we've got, which is some kind of 'dirty' location field, making it more fitted for what we are using it for atm (js translation) and also useful for the other issues. Other modules like l10n_client will also benefit of properly handled string locations.
|#39||locale_config_workflow-1777070-39.patch||32.59 KB||Jose Reyero|
|PASSED: [[SimpleTest]]: [MySQL] 46,049 pass(es).|
|#39||locale_config_workflow-1777070-39-interdiff.txt||10.41 KB||Jose Reyero|
|#33||interdiff.txt||2.97 KB||Gábor Hojtsy|
|#33||locale_config_workflow-1777070-33.patch||33.7 KB||Gábor Hojtsy|
|PASSED: [[SimpleTest]]: [MySQL] 42,786 pass(es).|
|#21||locale_config_workflow-1777070-20.patch||33.61 KB||Jose Reyero|
|PASSED: [[SimpleTest]]: [MySQL] 42,689 pass(es).|