-
Notifications
You must be signed in to change notification settings - Fork 142
New issue
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
V6 - Translation fallback #3038
Comments
I can confirm that I get errors in the network for |
@dimitriBouteille - this is correct behaviour for v6, as detailed in the "Breaking changes" here The component should not break, however, if the wrong locale is set. Is this actually happening or are you just seeing network errors for the non-existent language json? |
There doesn't seem to be a translation file for |
This issue is stale because it has been open 21 days with no activity. Please comment on this issue otherwise it will be closed in 7 days. |
Comment to keep open |
@sponglord - does Adyen accept external contributions? |
@ashrafnazar We have a third-party service to generate the translations for us. If you'd like us to support another language you can create another issue asking for it. We'll then check if it would benefit other merchants as well and, if it does, we'll ask our third-party service to generate the translation files (so no need to generate the files yourself). Also keep in mind that even if we don't support a language you can create your own custom translations. |
Describe the bug
Since the update of the module on v6, I have only problems ...
If I am not mistaken, on v5 there was a fallback system to use the parent locale if the local passed as argument of
AdyenCheckout
did not exist. Thus:The local
fr_CH
(fr_CA
, ...) does not exist in Adyen so it was the localfr_FR
that is loaded.On v6, if I pass the locale fr_CH, it is the translations en_US that are loaded...
To Reproduce
Steps to reproduce the behavior:
fr_CH
orfr_CA
localeExpected behavior
The parent locale must be loaded :
fr_CH
,fr_CA
=>fr_FR
it_CH
=>it_CH
de_AT
,de_CH
=>de_DE
The text was updated successfully, but these errors were encountered: