Open thedamon opened 4 years ago
In a setup where a component defines a prop through a mixin, the web-component that extends that component does not have access to the mixin's props
Pseudocode:
const mixin = { props: { 'test' } }; const base = { name: 'v-base', mixins: [mixin] }; const extender = { name: 'v-extender', extends: base } const mixiner = { name: 'v-extender', extends: base, mixins: [mixin] } extender.test // <-- not defined mixiner.test // <-- works
It's straightforward to work around this and may just be something that was never consciously implemented?
In a setup where a component defines a prop through a mixin, the web-component that extends that component does not have access to the mixin's props
Pseudocode:
It's straightforward to work around this and may just be something that was never consciously implemented?