Hey! Im having the same problem, but I would like to know why I cannot just import Router inside actions.ts and use it as I usually did on Javascript files. I know that it is something related to the router Quasar wrapper and I am getting really stuck on understanding why is this happening. Thank you.

@ioncoder your snippet were not showing what your state looks like before you were trying to mutate it so, it’s not also showing whether your function is really a vuex mutation function (you need to provide sufficient info next time.), you’ll need further reading into vue reactivity itself https://vuejs.org/v2/guide/reactivity.html#Change-Detection-Caveats. the one from vuex works because count already exist in the state object.

Hi @metalsadman thanks for answering, After you mentioned if I had vuex in the project I search more than I had it installed but I was importing the function wrong import { ...mapGetters } from 'vuex'; I fixt the error by importing it right. thanks again and sorry

ok thanks

@darshie the function is called slighly different in 0.17 my code is for v1 forgot to say LocalStorage.get.item(key) https://quasar-framework.org/components/web-storage.html#Getting-Started

Well, Quasar’s i18n is “native” to its components, meaning, the languages available and the i18n system is only for Quasar’s components. Needing the i18n object outside of the components is basically not necessary. You set it once in, say, a layout component and you are good to go for all further components, as the docs explain. Scott

Couple ways to go about it. One is to add a named export to your plugins and import that in stores. Another is to pass the vue instance to the store when dispatching actions Edit: You can access the vue instance from the store using this._vm

@Diferno said in q-uploader and vuex?: n my Vuex store I hi, Diferno can you plz share your code how you configure additionalFields in q-uploader. and how you receive that field from server side. thanks.

https://github.com/quasarframework/quasar/issues/479

And what about “tracking” the modal state itself? (opened/closed) and their acctions? (open, cancel, accept, etc.)