We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Vetur: Restart VLS
When a child component has both a modelValue and a value prop, Vetur incorrectly shows an error: <Component> misses props: model-value
modelValue
value
<Component> misses props: model-value
This is referenced by @muodov in this comment on Issue #2647 where he points to this line of code:
https://github.com/vuejs/vetur/blame/78171ae446a71982708556b3950f08cc4dd0bd01/server/src/modes/script/componentInfo.ts#L342
PR #2688 that closed #2647 added a vModelPropName that I believe would need to be applied to line 342 of componentInfo.ts:
vModelPropName
const vModelPropName = vueVersion === VueVersion.V30 ? 'modelValue' : 'value';
I generated a veturpack project with a component that demonstrates this issue: https://github.com/SharpSeeEr/vetur-v-model-value-bug
The text was updated successfully, but these errors were encountered:
It's a bug that comes from a PR. I will fix it.
Sorry, something went wrong.
0df3ad4
yoyo930021
No branches or pull requests
Vetur: Restart VLS
Info
Problem
When a child component has both a
modelValue
and avalue
prop, Vetur incorrectly shows an error:<Component> misses props: model-value
This is referenced by @muodov in this comment on Issue #2647 where he points to this line of code:
https://github.com/vuejs/vetur/blame/78171ae446a71982708556b3950f08cc4dd0bd01/server/src/modes/script/componentInfo.ts#L342
PR #2688 that closed #2647 added a
vModelPropName
that I believe would need to be applied to line 342 of componentInfo.ts:Reproducible Case
I generated a veturpack project with a component that demonstrates this issue:
https://github.com/SharpSeeEr/vetur-v-model-value-bug
The text was updated successfully, but these errors were encountered: