Closed davidshq closed 1 year ago
I'm inclined to agree, especially since we don't use it consistently. You make good points, so you have my support on this.
Great! I already discussed this with Curt when I initially made the changes and he was good with them, so I'll close this out and get a PR ready.
One of the changes I made to MIQA within the last ~2 months was removing
direct-vuex
- I'd like to push this change over but wanted to open up this issue for brief discussion in case anyone else things differently.My reasoning is as follows:
It breaks with Vue/Vuex conventions, e.g. normally one would use something like:
store.dispatch("someAction", somePayload)
Whereas direct-vuex uses something like the following:
store.dispatch.someAction(somePayload)
Another example is when using Vuex in components. Normally one might do something like:
Whereas with direct-vuex one can skip this step and use the store directly, e.g.
That said we do lose something by moving off the library:
Over the course of the last six months or so I've found the various problems that direct-vuex has caused me much more time consuming than any issues arising from removing direct-vuex.
Thoughts?