The issue we are running into is that our translations file is now hosted elsewhere, gotten only after the client has received which language the user wants the page in. When new translations are set with setTranslations, these strings do not rerender.
Changing langDOES cause a rerender, thus
A temporary solution I've found is to setLanguage("not_a_real_locale") before getting the translations, and then setting it back to the real language afterwards. This is not ideal.
In our app, we set the header of the page in many places like so:
The issue we are running into is that our translations file is now hosted elsewhere, gotten only after the client has received which language the user wants the page in. When new translations are set with
setTranslations
, these strings do not rerender.Changing
lang
DOES cause a rerender, thus A temporary solution I've found is tosetLanguage("not_a_real_locale")
before getting the translations, and then setting it back to the real language afterwards. This is not ideal.