support v-t directive about i18next-vue HOT 1 CLOSED

We don't currently plan to add a v-t directive, We try keep i18next-vue small and maintainable, so we'd rather not re-add the directives that @panter/vue-i18next had.

Using i18next's built-in fallback mechanisms can help with fallback/default translations. See https://www.i18next.com/principles/fallback for the various available options.

One way is to specify an empty translation for the key in the translation file (helloworld: "") and do something like
<p>{{ $t('helloworld') || 'Hello world' }}</p>

Alternatively, you can use the fallback-to-key approach, by specifying both the normal translation key and the fallback translation as an array of keys. This needs no entry in the translation JSON. This approach is probably the closest to v-t.
<p>{{ $t(['helloworld', 'Hello world']) }}</p>

Personally, I would prefer to use a fallback language using fallbackLng with default translations instead, and keep the translation in the Vue template simple, i.e.
<p>{{ $t('helloworld') }}</p>

from i18next-vue.