Skip to content
This repository has been archived by the owner on May 16, 2023. It is now read-only.

Chore: introduce compound text keys #116

Draft
wants to merge 1 commit into
base: release/3.3.x
Choose a base branch
from

Conversation

mlenkeit
Copy link
Member

@mlenkeit mlenkeit commented Sep 22, 2022

Texts components that are used multiple times can now be moved into a separate text key and referenced in a so-called compound text key. A compound text key must be of text type NOTR and thus will not be translated. In a compound text keys, other text keys can be included by referencing them with the syntax ${OTHER_TEXT_KEY}. The references are replaced at build time. Text that is not a reference is preserved. This allows for example to include line breaks, e.g. ${A}\n\n${B}.

Texts components that are used multiple times can now be moved into
a separate text key and references in a so-called compound text key.
A compound text key must be of text type `NOTR` and this will not be
translated. In a compound text keys, other text keys can be included by
referencing them with the syntax `${OTHER_TEXT_KEY}`. The references are
replaced at build time. Text that is not a reference is preserved. This
allows for example to include line breaks, e.g. `${A}\n\n${B}`.
@mlenkeit mlenkeit changed the title chore(i18n): introduce compound text keys Chore: introduce compound text keys Sep 22, 2022
@Ein-Tim
Copy link
Contributor

Ein-Tim commented May 13, 2023

This PR is obsolete. It can be closed.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants