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
In our previous projects we are using multi-language support with this strategy
pages/
[locale]/
home.tsx
about.tsx
for locale and identifying translations
and this will get locale from /en/about or /es/home so that it will identify which language it is using and set the text by that translation which is added in our locales folder
root/
locales/
en.json
es.json
But....
in our ever-rec project we are not using /[locale]/ folder by default and by adding this folder we have to update imports and little fit folder structure in order to use
if we want to use translations we have to update our folder structure from this
to this
Which will have some issues for us that we have to manually update all those imports which exists in every route
Sir @evereq and @paradoxe35 Brother please share your thoughts and help me understand should this is the best approach or not.
Add support to multiple languages for users.
The text was updated successfully, but these errors were encountered: