You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
foo.vue's class will be created during the initialization of its calling class.
This will end up applying all property decorators (eg, @Watch from https://github.com/kaorun343/vue-property-decorator) to Foo instead of the calling class.
To fix this, you need to change $decoratorQueue to a stack so that you can differentiate between properties applied to different reentrant class definitions.
The text was updated successfully, but these errors were encountered:
Could you explain more details what a problem you encounters?
I'm afraid I can't understand why we need to change $decoratorQueue to a stack.
I think it should be a queue to make consistent with the order of applying the native decorators.
Typing in the first textbox does nothing (doesn't display a message from the watch handler).
Commenting out components: { Child: require('child') } (or changing the language to Babel) makes it work.
Thanks for the repro. It seems like we need to assign $decoratorQueue for each class constructor to avoid to apply property decorators to wrong components.
When using the pattern of
foo.vue
's class will be created during the initialization of its calling class.This will end up applying all property decorators (eg,
@Watch
from https://github.com/kaorun343/vue-property-decorator) toFoo
instead of the calling class.To fix this, you need to change
$decoratorQueue
to a stack so that you can differentiate between properties applied to different reentrant class definitions.The text was updated successfully, but these errors were encountered: