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 switched my locale files from js to json to get the benefits of this package, there are still gaps though, for example, I build some translations dynamically out of the main set, which means I am now seeing erroneous no-missing-keys warnings, it'd be great to be able to use js-based locales
The text was updated successfully, but these errors were encountered:
After a few months the translations started to get unwieldy, so I've now broken them up into multiple json files that I stitch together with path-based rules for vue-i18n, and again I'm running into issues here, it'd be great there was an ability to supply a messages object ala vue-i18n so that I could thus construct it however I want and feed it into this plugin.
Also looking for support for locales in *.ts files. It took me a while to realize it's not supported yet (mainly thanks to this issue), perhaps a sentence or two in documentation mentioning supported file types for locales might be helpful for future users.
I switched my locale files from js to json to get the benefits of this package, there are still gaps though, for example, I build some translations dynamically out of the main set, which means I am now seeing erroneous
no-missing-keys
warnings, it'd be great to be able to use js-based localesThe text was updated successfully, but these errors were encountered: