-
-
Notifications
You must be signed in to change notification settings - Fork 54
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: Using Vue component with optional properties in Astro file cause type error #849
Comments
@Princesseuh Is this a known issue? Any idea on how to deal with this? |
I don't know, seems like a bug. I haven't investigated yet |
This may be related to #782. In VS Code I'm getting the 'no default export' error when I use defineProps with a default array, which led me to find that ticket and then this one. If you modify this ticket's sample code's Counter.vue's defineProps to add an array,
Instead of getting the original error from this bug you get the 'no default export' error instead. Also if you use the unmodifed example in #782 and run 'npx astro check' you also get the 'no default export' error (after removing the unused |
I manage to solve this issue by using |
That is indeed current limitation, defineProps works only with type definitions, not a easy problem to solve, but I think this should be documented as one of the limitations. https://github.com/withastro/astro/blob/bc2e74de384776caa252fd47dbeda895c0488c11/packages/integrations/vue/src/editor.cts#L40-L43 |
Describe the Bug
When I import a
Vue
component in an Astro file, it complains on optional properties when runningastro check
This seems to happen from
astrojs/check@0.5.5
Steps to Reproduce
Vue
component.astro
file without defining a value for the optional propertyastro check
Link to an reproducible example
The text was updated successfully, but these errors were encountered: