We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Localization files have to be loaded every time the page is loaded since there is no way to cache it by their filename.
Lets enable server to export localization .jsons with single definition .json file with this example content:
{ "languages": { "en": { name: "English", file: "en.7e2c49a622975ebd9b7e.json" } de": { name: "Deutsch", file: "de.6e2449a682975ebd9b6d.json" } } }
This could be also source for items in language select menu.
The text was updated successfully, but these errors were encountered:
Any progress with this?
Sorry, something went wrong.
Yes! Now it's possible to provide exported data using dynamic import or as an object. It's described in this doc page: https://tolgee.io/docs/web/using_with_angular/angular_preparing_for_production
JanCizmar
Successfully merging a pull request may close this issue.
Localization files have to be loaded every time the page is loaded since there is no way to cache it by their filename.
Lets enable server to export localization .jsons with single definition .json file with this example content:
This could be also source for items in language select menu.
The text was updated successfully, but these errors were encountered: