You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
when building the application, the locale files are transpiled to the built. Therefore they cannot be changed later on, like it is possible for the app-conf-*.json files.
Possible fix: replace require.context() in wegue/src/util/Locale.js (here and here) with a function that reads the files on demand. Maybe import is useful here.
@JakobMiksch This is the spot where all language files get picked up by webpack from the folder structure. As a second step the application and Wegue specific language files are merged into one big object.
Since one of the long term development goals is to separate Wegue and application code (e.g. deliver Wegue as a separate NPM package), IMO we should preserve the compile time packaging of Wegue core language files and only do dynamic loading for app language files.
On the fly merge with the built-in Wegue language files should be executed after loading an app language file (implementation simliar to the deep merge in the existing code)
On application start both app language files for the fallback language and the current language have to be loaded.
when building the application, the
locale
files are transpiled to the built. Therefore they cannot be changed later on, like it is possible for theapp-conf-*.json
files.useful links:
The text was updated successfully, but these errors were encountered: