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
When using v-slot, for example with RouterView, vudex-typecheck throws:
RouterView
vudex-typecheck
=> ./src/App.vue:4:27 Error :: Binding element 'Component' implicitly has an 'any' type. (code 7031) 2 | <Navbar /> 3 | <div class="container" style="margin-top: 70px"> 4 | <RouterView v-slot="{ Component }">
This obvious fix is to disable noImplicitAny, but I was wondering if it was possible to do better?
noImplicitAny
The text was updated successfully, but these errors were encountered:
Related RFC: vuejs/rfcs#192
Sorry, something went wrong.
Vetur fixed tracked this issue vuejs/vetur#2258 and silenced the error in the PR vuejs/vetur#2259.
Hello for future reader try :
<RouterView v-slot="{ Component }: { Component: Object }">
This should do the trick, for perfectionnists I think the original value in of VNode instance
Fixed in 7d1d193. Try pre-release build.
No branches or pull requests
When using v-slot, for example with
RouterView
,vudex-typecheck
throws:This obvious fix is to disable
noImplicitAny
, but I was wondering if it was possible to do better?The text was updated successfully, but these errors were encountered: