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
version: 0.37.3
<component :is="list"> <template #default="scope"> <slot v-bind="scope" /> </template> </component>
0.36.1 is not have this kind of lint issue.
The text was updated successfully, but these errors were encountered:
here is the minimal reproductive repo
https://github.com/exherb/vite-project
Run npm run lint will report
npm run lint
➜ npm run lint > vite-project@0.0.0 lint > vue-tsc --project . --noEmit src/components/HelloWorld.vue:9:10 - error TS2339: Property 'scope' does not exist on type '{ $: ComponentInternalInstance; $data: {}; $props: Partial<{}> & Omit<Readonly<ExtractPropTypes<{}>> & VNodeProps & AllowedComponentProps & ComponentCustomProps, never>; ... 10 more ...; $watch(source: string | Function, cb: Function, options?: WatchOptions<...> | undefined): WatchStopHandle; } & Readonly<...> & Sha...'. 9 {{ scope.msg}} ~~~~~ Found 1 error in src/components/HelloWorld.vue
related files: https://github.com/exherb/vite-project/blob/a63855d160259faea3ff4f823e7201fa83ef0fa8/src/components/HelloWorld.vue#L7
got time to check this issue? thanks @johnsoncodehk
Sorry, something went wrong.
For me it also started happening recently.
Slot scope variables used to default to any I believe, causing no issues throughout our app, but now suddenly we have a million of these:
any
Manually typing as was suggested somewhere else also doesn't work. Eg. #default="{ index }: { index: number }"
#default="{ index }: { index: number }"
@johnsoncodehk any idea for a work around?
2180f29
No branches or pull requests
version: 0.37.3
0.36.1 is not have this kind of lint issue.
The text was updated successfully, but these errors were encountered: