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.

Release notes snippet

Comments

Wim Leers created an issue. See original summary.

wim leers’s picture

Issue tags: +Configuration schema

Version: 10.1.x-dev » 11.x-dev

Drupal core is moving towards using a “main” branch. As an interim step, a new 11.x branch has been opened, as Drupal.org infrastructure cannot currently fully support a branch named main. New developments and disruptive changes should now be targeted for the 11.x branch, which currently accepts only minor-version allowed changes. For more information, see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 11.x-dev » main

Drupal core is now using the main branch as the primary development branch. New developments and disruptive changes should now be targeted to the main branch.

Read more in the announcement.