Vue.js: the good, the meh, and the ugly

Re:Vue.js: the good, the meh, and the ugly by parr0t on Thursday July 05, 2018 @06:51PM (#17467538)

This is essentially my chain of thought and what I have done. Even if it is a simple request that is confined to a single component when a developer looks at the codebase they can know that all API calls are called from Vuex modules and not modules _and_ components.

That then leads me to my next question though, if I am using Vuex to abstract the API calls is it bad practice to use Vuex actions for API calls that don't need to be saved into the store?

[ Parent | on HN ]

Re:Vue.js: the good, the meh, and the ugly by RussianCow on Thursday July 05, 2018 @09:32PM (#17468290)

I don't think it's bad at all to have an action trigger an API call that doesn't save anything to the store. However, as @mmcnl said in response to your original comment, you probably want to abstract the actual API-related code into its own module, so that you don't implement the API calls in the actions; then your actions become thin functions that simply call that code with the necessary parameters.

[ Parent | on HN ]