Add categorization to config translation mappers

Created on 13 January 2016, over 9 years ago

Updated 3 July 2025, 23 days ago

Problem/Motivation

All config translation mappers are usually loaded all together in an array ($container->get('plugin.manager.config_translation.mapper')->getMappers(), but we may need to treat them differently in contrib or core.

Proposed resolution

Add a categorization property. The three groups (in core) could be "Simple configuration", "Configuration entity", "Fields"

Remaining tasks

Verify this is acceptable for 8.1 and not considered an API break.

User interface changes

None.

API changes

API addition TBD.

Data model changes

None.

📌 Task

Status

Postponed: needs info

Version

11.0 🔥

Component

config_translation.module

Created by

🇪🇸Spain penyaskito Seville 💃, Spain 🇪🇸, UTC+2 🇪🇺

Live updates comments and jobs are added and updated live.

D8MI
(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.

language-config

stale-issue-cleanup
To track issues in the developing policy for closing stale issues, [Policy, no patch] closing older issues

Incomplete comments

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

Comment 23 days ago →
🇺🇸United States smustgrave
Thank you for creating this issue to improve Drupal.

We are working to decide if this task is still relevant to a currently supported version of Drupal. There hasn't been any discussion here for over 8 years which suggests that this has either been implemented or is no longer relevant. Your thoughts on this will allow a decision to be made.

Since we need more information to move forward with this issue, the status is now Postponed (maintainer needs more info). If we don't receive additional information to help with the issue, it may be closed after three months.

Thanks!

contrib.social Blog FAQ Discussions

Production build 0.71.5 2024