- Issue created by @Wim Leers
- 🇧🇪Belgium Wim Leers Ghent 🇧🇪🇪🇺
I think this would catch #3097497: system.site.page.front not translatable in UI, but works directly in config → too?
Drupal\Tests\config_translation\Functional\ConfigTranslationUiTest was failing in
📌
New config schema data type: `required_label`
Fixed
after translatable: true was added to some property paths that had type: string.
This seemed reasonable … but it turns out that due to the way that the config_translation module is implemented, only config schema types that have translatable: true set are effectively translatable. This appears to be intentional.
See above.
To make sure we do not regress against this, we should have an explicit kernel test that verifies every translatable config property path is indeed translatable through the UI. (Functional UI tests for every one of these would be far too slow/expensive.)
Write test.
None.
None.
None.
Active
10.1 ✨
Last updated
The change is currently missing an automated test that fails when run with the original code, and succeeds when the bug has been fixed.
(Drupal 8 Multilingual Initiative) is the tag used by the multilingual initiative to mark core issues (and some contributed module issues). For versions other than Drupal 8, use the i18n (Internationalization) tag on issues which involve or affect multilingual / multinational support. That is preferred over Translation.
I think this would catch #3097497: system.site.page.front not translatable in UI, but works directly in config → too?