-
-
Notifications
You must be signed in to change notification settings - Fork 16
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
Extract slot prop types from $$Slots
#273
Comments
Actually, in general, the parser should probably eventually support the whole RFC... |
I've also recently run into this. However, I don't understand why this doesn't already work. It seems like the code is sound.
return `${String(componentName)}['$$slot_def'][${JSON.stringify(
slotName,
)}][${JSON.stringify(letName)}]`; Which in your example should translate to My LSP & my other svelte tools have no problems understanding the type of the Does anyone know why this isn't working with eslint? I'd be happy to figure out how to fix this but I'm out of ideas right now. EDIT: I understand that nothing is generated for $$Slots, but I don't understand why this code to type the let binding exists if there are no corresponding types that are generated |
Description
In sveltejs/eslint-plugin-svelte#347 I proposed a rule to require slots and their props to be typed. In this package, those types should be used if they're present.
An example of what currently doesn't work:
App.svelte
:Component.svelte
:Here, on the marked line, I get the eslint error
@typescript-eslint/no-unsafe-call
- I presume that's because the parser does not infer thatarrayValue
is of typeArray<string>
and leaves it asany
...The text was updated successfully, but these errors were encountered: