Problem/Motivation
Drupal\Tests\config_translation\Functional\ConfigTranslationUiTest was failing in #3341682: New config schema data type: `required_label` 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.
Steps to reproduce
See above.
Proposed resolution
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.)
Remaining tasks
Write test.
User interface changes
None.
API changes
None.
Data model changes
None.
Comments
Comment #2
wim leersI think this would catch #3097497: system.site.page.front not translatable in UI, but works directly in config too?
Comment #3
wim leers