[SOLVED] QPopupEdit in QTable with Vuex data source - Do not emitted save event.

  • @metalsadman
    Your solution is not suitable for using vuex data source. In this case (v-model) I have vuex errors:

    vue.runtime.esm.js:619 [Vue warn]: Error in callback for watcher "function () { return this._data.$$state }": "Error: [vuex] do not mutate vuex store state outside mutation handlers."
    (found in <Root>)
    vue.runtime.esm.js:1888 Error: [vuex] do not mutate vuex store state outside mutation handlers.
        at assert (vuex.esm.js:87)
        at Vue.store._vm.$watch.deep (vuex.esm.js:763)
        at Watcher.run (vue.runtime.esm.js:4562)
        at Watcher.update (vue.runtime.esm.js:4536)
        at Dep.notify (vue.runtime.esm.js:730)
        at Object.reactiveSetter [as name_ru] (vue.runtime.esm.js:1055)
        at Proxy.set (vue.runtime.esm.js:1077)
        at callback (countries.vue?d101:136)
        at invokeWithErrorHandling (vue.runtime.esm.js:1854)
        at VueComponent.invoker (vue.runtime.esm.js:2179)
    (found in <Root>)

    In my component I use Vuex ds like this:

    <q-table ...  :data="ds">
      computed: {
          ds: state => state.ds.dsCustomers
          updateDocument: 'ds/updateCustomer',

    I also tested another case with the same Vuex errors:

      computed: {
        ds: {
          get() {
            return this.$store.state.ds.dsCustomers;
          set(value) {
            this.$store.commit('setDsCustomers', value);

  • @sontis you should make a local copy of your dsCustomers object that will be the one you pass in your q-tables data prop. still need more info probably make a codepen to show your minimal setup here.

  • It looks as your app is big enough to use this:


    In small use cases it is ok to create “spagetti” with those accessors/computed/events stuff, but in some point, the VueX querying is better. There are some other additional benefits: data models, normalization, easy synchronization.

  • i use this a lot too https://github.com/maoberlehner/vuex-map-fields. i would definitely try that vuex-orm one on future project, and would’ve used it in the huge project that i’m currently working on but alas i found out about it quite too late :(, and my partner not too open for refactoring smh.

  • Oh, that was my question too

  • @qyloxe thanks for the advice to use vuex-orm. But this thing does not solve data processing problems in the QPopuEdit. Could you show a working example?
    I see the following main problems in the QPopupEdit & Vuex:
    In case of v-model, QPopupEdit (QInput) emits input event that causes Vuex data modification error;
    In case of :value, QPopupEdit does not emit save event for correct Vuex data modification.

  • @sontis if your problem is based on unability to update Vuex, then this library surely solves that:

    if your problem is based on QPopupEdit component behaviour (events, model), then I do not have an opinion on that.

  • @qyloxe
    I think this is a QPopupEdit behaviour problem.
    Anyway, @qyloxe, thanks for the advice.

  • I just ran into the same issue. I agree with @sontis - the recommendations for workarounds are great, but are definitely workarounds. If QPopupEdit emits a “save” event with v-model, it should also emit a “save” event when binding value instead. At the very least, when buttons are turned on and the save button is clicked… @sontis have you tried using a computed setter? https://itnext.io/anyway-this-is-how-to-use-v-model-with-vuex-computed-setter-in-action-320eb682c976 I haven’t tried it yet, but will as soon as I have time. It allows using v-model with Vuex, without adding an ORM package. Might trick the save event into happening

  • @bfreed @sontis I don’t see why @save would trigger when you use :value in your q-input without using @input event on it, that’s a normal behavior https://vuejs.org/v2/guide/forms.html. Updated my pen using :value on both QPopupEdit and QInput https://codepen.io/metalsadman/pen/arLYOe. further reading about vuex https://vuex.vuejs.org/guide/forms.html#form-handling.

  • @metalsadman Thank you for the codepen!!
    I didn’t get that @save only fires if the value has changed. Makes sense now.
    Before writing my actions and mutations, I was trying to test with console logs, but since I wasn’t modifying my state (yet), the saves weren’t firing at all.
    @sontis: I’m grabbing the @save event on the q-popup-edit and calling an action to write to my API. On the q-input inside the popup, I’m grabbing @input and calling a mutation to set the vuex store.
    Now that the state is actually changing, q-popup-edit fires the @save event when I click the “set” button, and the API only gets hit then, not on every keystroke.

  • @metalsadman thank you for the codepen and the explanation. The code (with using @input event) now works, BUT:
    I have the following data processing GUI -> Vuex -> REST Api -> DB Store.
    And I have now the messy code, because,

    • In @input event handler in QInput need update ONLY Vuex store. I do not want to invoke REST api after each key press. For this I have mutation and in during editing in the QPopupEdit the Vuex Store is unsynchronized with the DB Store. At this time, all GUI elements using this data will show an incorrect value.
    • In @save event handler in the QPopupEdit need send data by REST and if response OK then update Vuex Store.
    • In@cancel event handler in the QPopupEdit need recover Vuex Store back.
      The worst is Vuex Store is unsynchronized with the DB Store at some point. All GUI elements (which used this data) will not be displayed correctly.

  • @sontis it’s there in my example, @save event you have access to the initialValue and the newValue, you only commit the newValue when all goes well and can still revert to initialValue if something fails. like i said this has nothing to do with vuex or whatever data source you are using, the idea is the same. It’s a pretty solid component tbh and I don’t think in this case there’s a need for something to change, since clearly the functionalities are working as they should be.

  • @metalsadman
    Your codepen consists code:

    <q-input :value="props.row.name" dense autofocus counter @input="v => {props.row.name = v}"></q-input>

    If you will be use Vuex Store as the data source for your QTable, then each key press in the QPopupEdit will be modificate Vuex Store data without vuex mutation. This will cause an error

    vue.runtime.esm.js:1888 Error: [vuex] do not mutate vuex store state outside mutation handlers.

    See posts above.
    Therefore, in the case of QPopupEdit + Vuex + Rest Api + DB I have the messy code.

  • @sontis hard to figure what you are actually doing in your vuex mutation, like i said in earlier post copy it first locally then that local data is what you should feed to your QTable’s data props then on your QPopupedit’s save event is where you call your actual vuex mutation/action. Per your thread’s title, there’s no issue there.

    About the vuex issue, would take some time for me to exactly emulate what’s wrong unless you provide a minimal pen of how you were doing it. I will try tho…

  • @metalsadman
    But then I have to have a local copy data source and synchronize it with the vuex data source.
    Why then need vuex? 🙂
    Sorry, I am not a native English speaker. Maybe I got a mistake with the thread’s title

  • @sontis you should mark as solved concerning the thread title since there’s nothing wrong with the event. your real issue was mutating your store, anyway here’s what i got https://codesandbox.io/s/q306jwnjx6 click “home” -> 'vuex table`, check the consoles, dunno if this is what you did, i would still suggest making a local copy and run your action/mutation @save event since that shows in vue devtools and is the vuex way of doing it.

  • @metalsadman thanks for good example.
    If you set Vuex strict mode in the “…/store/index.js”:

      const Store = new Vuex.Store({
        strict: true,
        modules: {

    then you see vuex errors after editing fields (check codesandbox console)

  • @sontis yep that’s why do my suggestion to copy it in local and do the mutation in the events. then in the watcher re assigned it to the local data. you should try to figure it out imo. the example is there to get you started.

  • @metalsadman
    “…suggestion to copy it in local…”
    In this case, I don’t need Vuex 🙂 (data duplication/synchronization)
    In Vuex Guide Form Handling recommends:
    “…The “Vuex way” to deal with it is binding the <input>'s value and call an action on the input or change event…”
    But the problem is that the quasar does not allow to mutate the properties of vuex storage objects.

Log in to reply