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
I was wondering if there would be a way to display the translation keys instead of the translation values, exactly the same way as a language/locale selector works for changing the language on page.
This would help to see where a particular translation key is in context, making it easier for translators to understand the context and make a translation that fits.
Thanks!
Note: if the fallbackLocale is set to empty string at init, later on setting a locale that does not exist will make the keys to be displayed on page. This is not ideal for production, but it can be a starting point for a better solution.
This could also be combined with import.meta.env.MODE, if using Vite, but that is not ideal either, even if it works to differentiate between production and other environments.
The text was updated successfully, but these errors were encountered:
Hello!
I was wondering if there would be a way to display the translation keys instead of the translation values, exactly the same way as a language/locale selector works for changing the language on page.
This would help to see where a particular translation key is in context, making it easier for translators to understand the context and make a translation that fits.
Thanks!
Note: if the
fallbackLocale
is set to empty string atinit
, later on setting a locale that does not exist will make the keys to be displayed on page. This is not ideal for production, but it can be a starting point for a better solution.This could also be combined with
import.meta.env.MODE
, if usingVite
, but that is not ideal either, even if it works to differentiate between production and other environments.The text was updated successfully, but these errors were encountered: