Allow access to setter mutations

[bodograumann]

When using the generateMutationSetters option, for each state property a mutation is generated, that sets the property.

Those setter mutations are only available inside of actions, not when using the module instance directly.

Do you think we should allow access from the outside? Or would you say that it is a much better practice to only do changes in the actions?

[gertqin]

So you want to do something like:

@Module({ generateMutationSetters: true })
class MyModule extends VuexModule {
  foo = "bar";
}
const myModule = new MyModule({ store, name: "myModule" });
myModule.foo = "baz";

?

It would not be hard to implement, but I'm not sure whether it is against the design principles of vuex (flux) or not. Do you think it would be beneficial to allow?

[bodograumann]

Yes this is what I mean.

I‘m not completely sure this follows the flux principles, but there are two reasons which let me lean towards yes:

• It is not the default setting, you have to enable generateMutationSetters.
• Even though the syntax is different, it simply commits a mutation, which is perfectly fine in flux as I understand it.

[gertqin]

Alright, I'll implement this. Although I think I'll keep it as an undocumented feature, as I'm still not sure whether this should be encouraged or not.