Skip to content
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

fix(runtime-core): v-model listeners that already exists on the component should not be merged #2011

Merged
merged 3 commits into from
Sep 2, 2020
Merged

Conversation

HcySunYang
Copy link
Member

Fix: #1989

@yyx990803
Copy link
Member

I adjusted it to a simpler heuristics: if a v-model listener (onUpdate:xxx) has a corresponding declared prop, then it indicates the user expects to handle the v-model logic in this component so it listener should not fallthrough.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Strange behaviour with prop inheritance (modelValue)
2 participants