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
Front end team has been working on a V2 Translate component. The aim is to remove redux dependencies from translations, so that new routes have as few dependencies from V1 as possible.
To cover in the PR we have been working on:
Migrate the Translate component to use atoms and not redux
Migrate the t function in the same way
If possible, use V2 translations API data structure
If possible, stop depending on redux for the initial state of the app
The text was updated successfully, but these errors were encountered:
We should check if the languages listed in /settings/languages are meant to be translatable. By default, they are not listed in the translationsV2 collection. They are currently translatable, and I understand that our system allows you to translate keys that are not present in the translationsV2 collection. I recall those not being translatable.
In any case, we need to remember that if a term is not present in the context users should still be able to translate it.
Front end team has been working on a V2 Translate component. The aim is to remove redux dependencies from translations, so that new routes have as few dependencies from V1 as possible.
To cover in the PR we have been working on:
Translate
component to use atoms and not reduxt
function in the same wayThe text was updated successfully, but these errors were encountered: