Sure, I don't see why you couldn't do that. I also like Vuex a lot, but the goal for me was to not have 2 libraries for managing state in an app and reduce my bundle size as much as possible.
I fail to see how it would be useful to have your actions in a Vuex store instead of your machine config though.
I fail to see how it would be useful to have your actions in a Vuex store instead of your machine config though.
It's just inertia. I currently use Vuex actions as a central place for API calls. Putting the actions into FSM would lead to some refactoring -- which is surely doable -- but I'd rather stick with the my approach if possible.
Sure, I don't see why you couldn't do that. I also like Vuex a lot, but the goal for me was to not have 2 libraries for managing state in an app and reduce my bundle size as much as possible.
I fail to see how it would be useful to have your actions in a Vuex store instead of your machine config though.
It's just inertia. I currently use Vuex actions as a central place for API calls. Putting the actions into FSM would lead to some refactoring -- which is surely doable -- but I'd rather stick with the my approach if possible.
Ok I see. I think you could just import your store in your fsm file and dispatch the actions from your machine.