(closed in favor of #19799) feat: allow for tree-shaking unused langauges translations in custom apps #19795
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
index.ts
files to re-export translations in TS for new langaugestranslations.ts
barrel files, to export each langauge in a separate public API members (to allow for treeshaking unused langauges)<featureName>Translations
the languages other thanen
(which were added only in the branch epic/tew-translation before)<featureName>Translations
(and<featureName>TranslationsChunksConfig
) in favor of favour the new non-prefixed conststranslationsEn
,translationsDe
,... for specific langauges (and non-prefixedtranslationChunksConfig
).By the way:
translation.ts
files andindex.ts
files. That said, the translation chunks configs were brought back manually laterTODO:
related to https://jira.tools.sap/browse/CXSPA-9131
OTHER STEPS not included in this PR:
{ en: translationsEn }