vuex-module-decorators VS vue3-realworld-example-app

The most important thing to realise is that the vuex-module-decorators class-based model behaves just like a vue-class-component under the hood.

This is my current favorite way to use TS+Vuex. It just clicks so much more in my head to do things like:

vuex-module-decorators: This one, I just realized, I use a little differently than I think is expected. Here is an example from their docs of what you can write and what it is equivalent to in "raw vuex":

If you're on Vue 2 I'd recommend this NPM https://github.com/championswimmer/vuex-module-decorators

Using https://github.com/championswimmer/vuex-module-decorators. Every module is 'dynamic' so you don't have to predefine your entire store in an object. here is a small example:

I'm using Vue to build out a little web app. I have a backend api already set up and now am trying to make calls to this api from my frontend. I've been using this public project for learning purposes: https://github.com/mutoe/vue3-realworld-example-app and I've taken some code from their src/utils, src/composable and src/services folders for properly setting up my fetch system. For example in their Profile.vue page located in src/pages/Profile, they get info for a profile by calling useProfile (from src/comspoable). Then useProfile calls fetchProfile, which calls get(), which then goes through a couple more functions in order to handle to response.

This might help https://github.com/mutoe/vue3-realworld-example-app