No prefix on exported APIs

[rchl]

Would it make sense to have those APIs named the same as in the Options API? I mean with the $ prefix?

vue-i18n-composable/src/index.ts

Lines 50 to 54 in a4579eb

	t: vm.$t.bind(vm),
	tc: vm.$tc.bind(vm),
	d: vm.$d.bind(vm),
	te: vm.$te.bind(vm),
	n: vm.$n.bind(vm)

[kazupon]

That good point!
vue-i18n-composable is vue-i18n Composition API for Vue 2.x.
So, We only provide a few APIs, but from now on, vue-i18n-composable will support to back-port from [email protected]

[rchl]

So what do you mean by that? That it's something that is worth adding or not?

That said, I guess vue-i18n exposes $t and co. in the template anyway so this is just a complementary API and maybe doesn't need to follow the same naming convention...

[kazupon]

I mean that the Composition API provided by [email protected] is back-ported to this package.
The APIs prefixed with $ are not going to be exposed. We're not going to expose the API prefixed with $, because as you said, it's already provided in the options API
From now on, The reason for enhancing this package is to support users who are using Vue 2.x + @vue/composition-api to migrate to Vue3 + [email protected] using the Composition API. 2️⃣ ➡️ 3️⃣