The previous approach with using separate domains and then doing multi- domain lookup made it hard for branding to hook into the process later. This introduces an alternative approach where all the domains are merged into the default app domain. The domains are still kept around separately in anyone wants to perform translations using a specific domain.
Related issues
Bug #36330: Translated strings are not loaded for plugins into the browser, leading to react-based frontend not having translations
Added by Adam Ruzicka 11 months ago
Refs #36330 - Use merged translations
The previous approach with using separate domains and then doing multi-
domain lookup made it hard for branding to hook into the process later.
This introduces an alternative approach where all the domains are
merged into the default app domain. The domains are still kept around
separately in anyone wants to perform translations using a specific
domain.