cannot use Vue i18n in slot templates

Reported by @AbrahamBrookes in #14:

It seems that using the new slot feature breaks reference to my root vue app? I have a component that sits inside the eventContent slot, and I can no longer access my root vue instance (in particular, my vuex store) from that component:

		<full-calendar 
			:options="calOptions"
		>
			<template v-slot:eventContent="event" >
				<planner-period
					:event="event"
				></planner-period>
			</template>

		</full-calendar>

Inside the planner-period component when I try to access my store data using this.$store.state I get this.$store is undefined. Is the calendar creating its own entirely new vue app?

[arshaw]

I’ve merged the PR and released everything in v5.4.0!

[rangermeier]

I’m wondering, as a workaround, could you somehow initialize the i18n plugin globally, using Vue.use(VueI8n) (like here)?

@arshaw I don’t think this would suffice. You still have to pass in the same i18n instance as option when initializing the Vue instance for the event content, as shown in https://kazupon.github.io/vue-i18n/started.html#javascript

Building on the attributes proposal from @kgilden: Maybe it’s possible to extract all non-default properties from this.$root.$options which would boil down to i18n, store, router, or whatever option is injected to the root Vue instance. That way the user wouldn’t have to replicate her intial Vue setup and still could make use of her Vuex store, i18n, or router state inside the scoped slot.