-
-
Notifications
You must be signed in to change notification settings - Fork 48
CustomEvent
s are treated as any
#432
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Comments
Thank you for posting the issue. However, I still don't know how to solve it. Plain So now it's better to assign Also related to issue #298. Combining with the experimental parser |
FYI, I changed the parser to only improve type definitions when using typescript-eslint-parser-for-extra-files. |
it seems that |
Did you use typescript-eslint-parser-for-extra-files? Please provide a reproduction repo if you use it. If not, please don't send spam. |
Svelte5 doesn't need to use |
Before You File a Bug Report Please Confirm You Have Done The Following...
What version of ESLint are you using?
8.33.0
What version of
eslint-plugin-svelte
are you using?2.25.0
What did you do?
Configuration
asdf.svelte
main.svelte
What did you expect to happen?
no error, as
e.detail
isnumber
, notany
What actually happened?
Link to GitHub Repo with Minimal Reproducible Example
https://github.com/DetachHead/eslint-plugin-svelte-repros/tree/3a6151d1f80aacf9246db66758276bb8869f0721
Additional comments
related: #390
the issue was fixed for events with
currentTarget
, but not forCustomEvent
sThe text was updated successfully, but these errors were encountered: