Namespaced modules still broken about vuex-class-component HOT 8 CLOSED

This issue has been resolved in the latest version

from vuex-class-component.

It seems like the options are used of the last extracted module, or something like that...

export class StoreA extends createModule({ namespaced: "StoreA", strict: true }) { }
export class StoreB extends createModule({ namespaced: "StoreB", strict: true }) { }
console.log(extractVuexModule(StoreA));
console.log(extractVuexModule(StoreB));
export class StoreC extends createModule({ namespaced: "StoreC", strict: true }) { }
console.log(extractVuexModule(StoreA));
console.log(extractVuexModule(StoreB));
console.log(extractVuexModule(StoreC));

prints

{StoreB: {…}}
{StoreB: {…}}
{StoreB: {…}}
{StoreB: {…}}
{StoreC: {…}}

from vuex-class-component.

Seems very likely this has something to do because you're using the prototype here, which is always VuexModule:

from vuex-class-component.

Mind sharing a sample project so I can replicate your issue.

Thanks

from vuex-class-component.

Here you go. I've added some console.log's to src/store.ts

yarn install
yarn serve

https://github.com/SaphuA/vuex-class-component-ns-repro

from vuex-class-component.

Looks ok! I'll do some more testing this week.

from vuex-class-component.

So when exactly should one use createModule and when With for providing options?

from vuex-class-component.

With is useful for extending already defined options.

Ideally you want to create a base configuration like so:

const VuexModule = createModule({
  strict: false,
  target: "nuxt",
  enableLocalWatchers: true,
})

export class UserStore extends VuexModule.With({ namespaced: "user", strict: true }) {
}

Think of it as a 2 level inheritance for your module options.

from vuex-class-component.