-
-
Notifications
You must be signed in to change notification settings - Fork 860
Translation file placeholder #725
Comments
I am sorry but I do noy understand what is your problem and what improvements you expect in vue-i18n. |
when you don't have a translation file in other language, its hard to test if every text is in $t() format here im missing |
OK, I understood your technique to distinguish translated/non-translated strings visually by adding icons. BTW, if fallback translation showed, a meesage like "Fall back to translate the keypath 'hello' with 'en-US' locale." will be displayed in the console.
The technique sounds useful for QA, but I think it should not be enabled by default in vue-i18n itself, since such icons should not be displayed in the app in production,. To distinguish translated/non-translated strings visually (not only log in console), I will propose "FallbackHandler" that allows changing strings in case of fallback, so we may add icon (❌ or 🔥 ) to the fallback locale strings. |
Yah that sounds great ( the 🔥 is better)
it could have a function in VueI18n constructor that grabs the message object and transforms it
|
Thank you for your feature request! However, we need to verify a little more whether this feature breaks other features (e.g. linked messages, Component interpolation, ... etc), due to this feature change locale messages.
In particular, this should be handled a little more strictly. |
I have an existing project and im start to implement i18n, but its a little hard to me to see every text that needs to be transformed into $t in my app and we don't have any translations yet making it impossible to the QA team test. Then i made this simple file that put a emoji ✅ in front of every word/phrase based on a 'complete' translation file
this file could be in the docs, or in the files that the plugin changes
The text was updated successfully, but these errors were encountered: