Skip to content

fix: false positives for <svelte:fragment let:x> in no-undef #147

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

Merged
merged 2 commits into from
Jan 3, 2022

Conversation

ota-meshi
Copy link
Member

@ota-meshi ota-meshi commented Nov 26, 2021

fixes #146
fixes #109

package.json Outdated
@@ -37,7 +37,7 @@
"@rollup/plugin-node-resolve": "^11.2.0",
"@typescript-eslint/eslint-plugin": "^4.14.2",
"@typescript-eslint/parser": "^4.14.2",
"eslint": ">=6.0.0",
"eslint": "^7.0.0",
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The test fails when using ESLint v8.

Copy link
Member

@dummdidumm dummdidumm left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me. The failing tests on v8 are handled in #142

@dummdidumm dummdidumm merged commit 1c92799 into sveltejs:master Jan 3, 2022
@ota-meshi ota-meshi deleted the fix branch January 3, 2022 12:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

using 'let:' variables with aliases will give you 'not-undef' errors with Eslint. Slot props producing no-undef on <svelte:fragment>
2 participants