No More Posting New Topics!

@oussama-he make your router/routes.js a function that accepts a store parameter from your router/index.js. example:

// src/router/routes.js ... const routes = (store) => [ ... beforeEnter: (to, from, next) => { if (store.getters.isAuthenticated) { console.log('authenticated user'); next('timeline') } else next() } ... ] export default (store) => routes (store) // src/router/index.js import routes from './routes.js' export default function ({ store }) { // <-- accepts store as parameter const Router = new VueRouter({ scrollBehavior: () => ({ x: 0, y: 0 }), routes: routes(store), // <--- pass the store context to your routes.js ...

@forevereffort

You’re changing state outside of a mutation. Where that happens is unclear from the warning logs. You’ll have to investigate that yourself more.

maybe:

state.fileWatcher.close()

@forevereffort

Sure if it works and you have types now.

@tc Hi,
Just like you are using storage plugin as I’m using advance HTTP plugin.
Cordova loads plugins after when device is ready. If you try to use plugin directly when app is booting then these plugins would not be available. So I used “deviceready” event to access http plugin and you can use the same event.

@ytsejam

I think it is used as “this._vm.axios”, but did not work for me I have found this boot solution.

For one thing, you would need to access it as: this._vm.$axios because you put a $ in front on the prototype definition
Second, I don’t know how you are writing your functions but the this will be inforrect if you used fat arrow (=>) – they need to be functions for this to be referencing the store.

@dobbel yes because it’s a function, in the boot is different, the store instance is passed as a parameter it’s the same store instance in your src/store/index.js, you’ll get more context if you check .quasar/client-entry.js file (if I’m not wrong), to see how those are initialized, you’ll also see there why $router instance is accessible in your stores via this.$router (if you are using function instead of arrows). I suggest you check that folder out in your project.

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.

@BillD http://shzhangji.com/blog/2018/04/17/form-handling-in-vuex-strict-mode/

I think the ‘Computed Property’ way with get/set is the best approach. So you can still use v-model.

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.)