-
Notifications
You must be signed in to change notification settings - Fork 1.4k
fix(eslint-plugin): detect node API usage more accurately #7664
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
base: build/v2
Are you sure you want to change the base?
Conversation
Build/v2
🦋 Changeset detectedLatest commit: 8595ea9 The changes in this PR will be included in the next version bump. Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
commit: |
built with Refined Cloudflare Pages Action⚡ Cloudflare Pages Deployment
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure what this tests? Is there anything in this code that would be flagged with or without the qwik plugin?
…prove edge case handling
…efault forbidden APIs
packages/eslint-plugin-qwik/tests/scope-use-task/invalid-scope-use-function.tsx
Outdated
Show resolved
Hide resolved
packages/eslint-plugin-qwik/tests/scope-use-task/valid-scope-use-return-object.tsx
Show resolved
Hide resolved
|
@wmertens done |
…se-return-object test
What is it?
Description
I enhanced the
qwik-eslint-pluginto support two edge cases:initin aVariableDeclaratorin AST.2.When path is used as a property key inside an object.
adding two situations
Checklist
pnpm change