Replies: 1 comment
-
I got it working, both nested and root boundaries. I had something misconfigured in my i18next config that was causing it to always hit the fallback language. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I'm trying to localize error boundaries within my app and having difficulty. In both the root.tsx and other nested boundary's I'm able to use the
t
function but I always get English. I'm assuming it's always hitting my fallback language. I'm not able to use loader data which is where the docs say to get the locale value from.I've tried getting the language from
navigator.language
and forcing it in thet
function like so (t("some_key", { lng: navigator.language })
) but that doesn't work either (despite correctly tracing out a non-english code).I found this discussion from almost two years ago. Is it still relevant? Is there any update on how to use translations in error boundaries? Discussion here: #33
Beta Was this translation helpful? Give feedback.
All reactions