-
-
Notifications
You must be signed in to change notification settings - Fork 4.1k
Component cannot be inspected when prop has null in type array #1559
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
Labels
Comments
I managed to reproduce the issue using a fresh vue-cli typescript project, with minimal setup on top. https://github.com/senritsu/vue-devtools-issue-reproduction-1559 Same behavior as in the original issue report, same OS/Browser/etc. |
This has nothing to to with Typescript, the real issue is inspecting a component with a prop having export default {
props: {
foo: {
type: [Number, null]
}
}
} |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Version
6.0.0-beta.17
Browser and OS info
Chrome 93 / Windows 10
Steps to reproduce
script setup
syntactic sugarconst props = defineProps<{ modelValue: Foo[] | null }>()
What is expected?
Component can be inspected
What is actually happening?
Infinite errors in console
Component inspector panel stays empty.
Using the "old" syntax to defineProps
works like expected, but is considerably more verbose.
The text was updated successfully, but these errors were encountered: