rfox12

Vuex has created a lot of pain for Typescript users. Now that we have the Composition API... do we even really need Vuex? In 2020, if I'm training a team...

A shout out to @paleo, [direct-vuex](https://www.npmjs.com/package/direct-vuex) is fantastic. Strongly typed coding within the store **and** (perhaps more importantly) when components access the store state and actions. I tried Vuex 4...

I'll add two additional compelling reasons to keep Vuex in Composition API world: - Support for Hot module reloading - The string descriptors can be useful if you need to...

I second the notion! Also if we can add to this request.. an "expand all" option?

After spending very many hours on "my utlimate Vue setup" I've found that JS/TS errors in the *template* is really the missing ingredient for me. I *want* to see error...

I'm using the Composition API as a plug-in for now (w/Vue 2.6). Vuex 4 just came out, but as far as I can tell you shouldn't really need to change...

Maybe you could move these lines out of `index.d.ts` and into a new `socket.d.ts` file? ```ts import { VueDecorator } from 'vue-class-component'; export const Socket: (eventName?: string) => VueDecorator; ```

+1 for interoperability between Jackson and Classmate (two solid dependencies for me). In my case lots of good introspection is performed by Jackson... then repeated by Classmate. Unless... Is there...

I won't be so bold as to make an ask. After doing some digging on my own I arrived at what you just told me... no easy path. I love...

I think this is a pretty common issue with JSON schemas. https://stackoverflow.com/a/23001194/5153063 Solutions seem to have all sorts of ugly duplication involved. Maybe this is why the `ajv` library seems...