Use getMessageFallback to provide fallback to default locale

[moy2010]

Hi everyone! I'm wondering if there’s any way to use getMessageFallback to provide a fallback to the default locale.

The reasoning for this is that a key might be missing in one locale file, and I would like to show the English translation as a fallback rather than an error message.

I couldn't find any API that would leverage the fact that we have the namespace and the key for the missing translation.

[amannn]

Hello @moy2010 and thanks for the question! As this has come up before, I thought it might be a good idea to include a section about this in the docs.

Can you let me know if this looks useful to you?

https://next-intl-80nf5cxec-amann.vercel.app/docs/usage/error-handling#fallbacks-from-other-locales

Relevant PR: #124

[moy2010]

Hi Jan! Yes, the PR looks great! Thanks :D

[moy2010]

Btw, I came up with a different solution by fetching the english messages on a component wrapping NextIntlProvider, so that they could be used within getMessageFallback. That way I can still get alerted of a missing key :).

[amannn]

Hey, good to hear! That's a viable solution, just note that it might have a performance impact since you're loading two locale bundles now.

Thanks for checking out the PR! 🙂

[moy2010]

Indeed. That's the compromise I have to accept for now.