Cache invalidation about i18next-browser-languagedetector HOT 5 CLOSED

Ah, i see. There is not much we can do in this case...it's just a detector and persisting mechanism. While there is an options expiration for cookies - there is nothing similar to localStorage. Also resetting that automatically might lead to more problems the road down as users might not want that.

Like always the best option is to give your users an option to toggle that language - this way they can change the language anytime it gets added.

from i18next-browser-languagedetector.

Can you more explain what you mean by:

My user accessed the app before I added their browser's default language. Now they see English instead of French.

How do you set the language?!?

from i18next-browser-languagedetector.

Not sure why the extra punctuation.

I don't set it explicitly. I use this plugin to automatically detect the language.

Scenario in detail:

• User accessed app before French translations existed.
• This plugin (or i18n-next react?) set a local storage prop (i18nextLng) to EN.
• I deployed a new version of the app containing French translations
• The user still sees English.

So basically I have users who should now see French translations (because that is their navigator.language prop, but instead see English because of the LS i18nextLng prop.

from i18next-browser-languagedetector.

Like always the best option is to give your users an option to toggle that language - this way they can change the language anytime it gets added.

FWIW that's what we do @bidalihq.

You can also get them to manually run localStorage.clear() in their console. 🤷‍♂️

from i18next-browser-languagedetector.

For react-query I added the locale/language that is also sent to the API (Accept-Language HTTP request header) to the cache key (array). I hope this allows to easily invalidate the request caches when the locale is changed.

from i18next-browser-languagedetector.