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
I'm not 100% sure if this is an error in cli or i18next.
We use locize to manage translations. We have added translations for spanish US (es-US) and use english (es-US) as default language. We are using our custom cloudront cdn as primary and locize cdn as fallback.
While downloading translations using cli, 'es-US' and 'en-US' translations are downloaded 馃憤 . But i18next tries to load the translations for 'es' also which gives an error from cloudfront (as 'es' translations were not downloaded by locize cli and not pushed to cdn). Since we use locize as fallback, i18next tries to load es translations from locize which returns empty object.
From the screenshot:
First 3 calls are made to cloudfront to load translations for en-US, es (returns 403 as translations aren't there), es-US respectively.
4th call is made to locize to load translations for 'es' which is a success and returns empty object
Expected behavior
Either cli should download the translations for 'es' also so that we can push it to cdn and that API call to load 'es' translations doesn't return an error or i18next should not load translations for 'es'.
Your Environment
runtime version: i.e. node v14
module version: 7.12.7
os: Mac
The text was updated successfully, but these errors were encountered:
馃悰 Bug Report
I'm not 100% sure if this is an error in cli or i18next.
We use locize to manage translations. We have added translations for spanish US (es-US) and use english (es-US) as default language. We are using our custom cloudront cdn as primary and locize cdn as fallback.
While downloading translations using cli, 'es-US' and 'en-US' translations are downloaded 馃憤 . But i18next tries to load the translations for 'es' also which gives an error from cloudfront (as 'es' translations were not downloaded by locize cli and not pushed to cdn). Since we use locize as fallback, i18next tries to load es translations from locize which returns empty object.
From the screenshot:
Expected behavior
Either cli should download the translations for 'es' also so that we can push it to cdn and that API call to load 'es' translations doesn't return an error or i18next should not load translations for 'es'.
Your Environment
The text was updated successfully, but these errors were encountered: