You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using this package and the standard receive mutation appears to not be adding new items to the byId state in a "Vue-reactive" way. When I mapped the list getter to a computed value and used that as a v-model to a Vuetify combovox, the computed value was always empty even after the state.byId had been updated.
The README file says that the code generated for this mutation does this: response.forEach(datum => Vue.set(state.byId, datum.id, datum));
but the project code in mutations.js does this: response.forEach(datum => (state.byId[getKey(datum)] = datum));
Should the receive mutation be updated to use Vue.set? I can submit a pull request with this change.
The text was updated successfully, but these errors were encountered:
I'm using this package and the standard
receive
mutation appears to not be adding new items to thebyId
state in a "Vue-reactive" way. When I mapped thelist
getter to a computed value and used that as av-model
to a Vuetify combovox, the computed value was always empty even after thestate.byId
had been updated.The
README
file says that the code generated for this mutation does this:response.forEach(datum => Vue.set(state.byId, datum.id, datum));
but the project code in
mutations.js
does this:response.forEach(datum => (state.byId[getKey(datum)] = datum));
Should the
receive
mutation be updated to useVue.set
? I can submit a pull request with this change.The text was updated successfully, but these errors were encountered: