You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was a bit confused, because I couldn't reproduce no-unsafe-* issues, because imported component seems to have correct type now. However your reproduction still seems to have the same issue:
I also found another unrelated issue when comparing your .vue and tsx code:
vue-tsc didn't catch type issue with renderer option not matching prop.renderer type.
Checklist
Tell us about your environment
Please show your full configuration:
What did you do?
I have a child component in Vue3LottieWeb.vue file, whose
setup()
function returnsplay
,stop
methods.In parent component, I import that child component and use as template ref:
What did you expect to happen?
ESLint should not raise error.
What actually happened?
ESLint complains with "Unsafe assignment of an
any
value @typescript-eslint/no-unsafe-assignment"When I hover the code in VS Code, Vetur successfully deduces the type of
bell
andbell.value
, but ESLint not.Repository to reproduce this issue
https://github.com/hongquan/failed-eslint-vue-ref-child-component
The text was updated successfully, but these errors were encountered: