Updating a model via constructor causes a Vuex error

As of v1.7.0, creating a new record in the store works fine like so:

new $nuxt.$FeathersVuex.User({
  "id": "doug",
  "name": "Doug Bowser",
});

A new record is added to the store, reactivity seems to work fine. Calling the constructor with exact same data again also causes no errors. However, calling the constructor with an existing id and modified data causes a Vuex error:

new $nuxt.$FeathersVuex.User({
  "id": "doug",
  "name": "Doug Bowsette",
});

vue.runtime.esm.js:1887 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:4529)
    at Watcher.update (vue.runtime.esm.js:4503)
    at Dep.notify (vue.runtime.esm.js:730)
    at FeathersVuexModel.reactiveSetter [as some] (vue.runtime.esm.js:1055)
    at utils.js:276
    at Array.forEach (<anonymous>)
    at updateOriginal (utils.js:250)
    at new FeathersVuexModel (model.js:44)

Using store.dispatch('orders/addOrUpdate', newRecord) does not have the same issue, however.

[NickBolles]

Both are related to getting records from the Vuex store.

In both cases, calling New on a record not on the store works fine. But the second time (with an ID) it doesn’t. But my particular case was because of the SSR store. Although I ran across the same issue you are describing too.

Similar reproduction steps, not the same issue. But it’s worth linking the issues together IMO.

[marshallswain]

I’m going to close this since it’s fixed in the pre-release.