fix: respect proto

[andrewvasilchuk]

🐛 The bug
When state is an instance of a class, prototype chain is lost.

🛠️ To reproduce
Steps to reproduce the behavior:

import Vue from 'vue'
import Vuex from 'vuex'

import { useAccessor } from 'typed-vuex'

class Car {
  constructor(public name: string) {}

  setName(value: string) {
    this.name = value
  }
}

const state = new Car('BMW')

const mutations = mutationTree(state, {
  mutation(state, name: string) {
    state.setName(name) // OK
  },
})

const storePattern = {
  state,
  mutations,
}

const store = new Vuex.Store(storePattern)

export const accessor = useAccessor(store, storePattern)

accessor.setName('name') // Error, prototype chain is lost

🌈 Expected behaviour
Prototype chain is preserved.

ℹ️ Additional context
Consider using Object.create here.

[danielroe]

I really appreciate these bug reports - thanks @andrewvasilchuk.

On this occasion it looks like Vuex isn't meant to be used with classes in state - see https://vuex.vuejs.org/guide/state.html#single-state-tree.

Discussion welcome, however.

[andrewvasilchuk]

Yes, but the accessor behaves like a transparent proxy/decorator, so to be even more transparent it should preserve prototype chain.