privatenumber / vue-proxi Goto Github PK

This is a comparison between Reactive Provide and Proxi to outline differences in purpose and how one is not necessarily an alternative to the other.

	Reactive Provide 0.3.0	Proxi 1.0.0-beta.1
Purpose	To provide a reactive object given a list of properties from the Parent VM	To proxy data applied to the <proxi> to a targeted Child component instance
Uses provide/inject	✅	✅
Has template API	❌	✅ Founded on the idea that component communication should remain in the template instead of re-invented
Passes down attrs, props, listeners attached to the Parent	✅	✔️ Not primariy use-case but possible with <proxi v-bind="{ ...$props, ...$attrs}" v-on="$listeners">
Parent can bind arbitrary class, attrs, props, listeners to the Child	❌ You can pass down any property from Parent VM but won't be bound	✅ listeners and props automatically bound to Child, class available in this.$$.class, attrs available in this.$$.attrs
Child can pass down injected attrs and listeners	❌ The injected data is merged into a single object. Would require filteration	✔️ v-bind="$$.attrs" v-on="$$.listeners"
Dependents
Install size
Bundle size

I see typescript errors when trying to use the injected props in my child component. Typescript is unable to find these injections. The code renders locally, but these typescript errors break the build of my application.

Things I've tried

1. This works as expected, but I get this breaking typescript error

2. This does not work, and gives me this typescript error. I thought this might work because this was shown in the documentation.

The Solution I'd Like

I would like to be able to access my props directly this.myProp or through some const to make it clear that it's injected like this.ProxiInjection.myProp without any typescript errors

Reproduction

You can explore a reproduction of this error here: https://codesandbox.io/s/vue-typescript-example-forked-x4h98x?file=/src/App.vue