-
-
Notifications
You must be signed in to change notification settings - Fork 33.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Vue.extend causes nested mixins to be merged twice #8865
Comments
Don't use Vue.extend on a mixin, a mixins are plain objects |
Not if you use typescript they aren't. |
Can you provide an example of how to handle this when using typescript @posva ? |
KaelWD
added a commit
to KaelWD/vue
that referenced
this issue
Sep 30, 2018
13 tasks
yyx990803
pushed a commit
that referenced
this issue
Nov 30, 2018
f2009
pushed a commit
to f2009/vue
that referenced
this issue
Jan 25, 2019
aJean
pushed a commit
to aJean/vue
that referenced
this issue
Aug 19, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Version
2.5.17
Reproduction link
https://codepen.io/anon/pen/ReNVra?editors=0011
Steps to reproduce
Open the console
What is expected?
What is actually happening?
MixinB.options
still hasmixins
, which gets applied again if used inmixins: []
orextends:
even thoughVue.extend()
has already done thatThe text was updated successfully, but these errors were encountered: