-
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: c936c82 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
|
packages/eslint-plugin-qwik/tests/scope-use-task/valid-scope-use-return-object.tsx
Show resolved
Hide resolved
…prove edge case handling
…efault forbidden APIs
} | ||
|
||
if (variable.defs.length === 0) { | ||
if (variable?.defs.length === 0) { |
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.
because you removed the !variable test, now you needed to add this. Just add the !varaible test again
import { component$, useTask$ } from '@qwik.dev/core'; | ||
|
||
export default component$(() => { | ||
function child_process() {} |
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.
this is valid code, because it shadows the global child_process, and shouldn't fail the eslint test
What is it?
Description
I enhanced the
qwik-eslint-plugin
to support two edge cases:init
in aVariableDeclarator
in AST.2.When path is used as a property key inside an object.
adding two situations
Checklist
pnpm change