Stores cannot be used before lifecycle hooks about pinia HOT 6 CLOSED

yes, it breaks current instance because it creates one itself to outlive component scoped for the state, but creating it outside of a component, by calling useStore for the first time, doesn't break any current instance 🙂

from pinia.

Yeah, this is a limitation that needs to wait for vuejs/rfcs#212. For now, it's necessary to call the useStore function at the end of setup or call pinia.store(useStore) for each store in your main.js file (it will also remvoe the code splitting)

from pinia.

I am wondering whether there is an easier way to call pinia.store for all stores. Currently this feels like the biggest issue for me as moving things around setup function does not make it readable or maintainable. Also not always possible and required multiple instances of pinia stores around one setup function.

In some compiled language I would use reflection to register stuff like that within an assembly. Doesn't seem like the mentioned RFC got a lot of positive feedback 😰

from pinia.

It's annoying for me too. The easiest workaround is to import all stores in your main.js file and call pinia.store(useStore) to instantiate them.

The RFC will go through a way or another because there is a need for it

from pinia.

Thanks I will end up doing that. Generally is this the same reason why this is happening?

const firstInstance = getCurrentInstance(); //resolves properly
const userEditStore = useSomeStore();
const secondInstance = getCurrentInstance(); //always null

This seems to be the reason why useVuelidate which is internally calling getCurrentInstance is failing. I wanted to bind vuelidate directly to my store state so I will just import all stores at start like you mentioned.

from pinia.

@posva

I use pinia^2.0.13 in vue2, and postinstall npx vue-demi-switch 2, alll ok.
but when i use onBeforeMount or others Lifecycle in setup, how can i resolve it?

from pinia.