-
Notifications
You must be signed in to change notification settings - Fork 116
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
bug: Vue output modelValue is required #233
Comments
Hello @markbrockhoff thanks for the issue and the PR! I agree that the type is too strict and should be optional in this case. Would you be able to create a simple reproduction app with one of the problematic dependencies that conflicts with the types? This will help in my ability to confirm your PR resolves the problem correctly and can help improve the review/merge time. Thanks! |
Hi @sean-perkins thanks for the quick response. |
Thanks @markbrockhoff! I'll try to clone and validate this weekend, Monday at the latest. |
@sean-perkins Do you know when this fix will be released? It'd be great if we could install and use the new version as soon as possible. |
Thanks for the issue! This issue is being locked to prevent comments that are not relevant to the original issue. If this is still an issue with the latest version of the output targets, please create a new issue and ensure the template is fully filled out. |
Hello,
I noticed that the generated types for Vue always require the property v-model to be defined.
This becomes especially noticeable when using tools like vue-tsc or volar for typechecking a vue project.
From my understanding, this comes from the interface
InputProps
defined in the generated file vue-component-lib/utils.ts.Simply making the property
modelValue
optional seemed to fix the problem in my testing.I already created a small PR to implement the suggested fix: #234
The text was updated successfully, but these errors were encountered: