-
-
Notifications
You must be signed in to change notification settings - Fork 466
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
linter: followups for react/exhaustive-dep
#7246
Comments
✅ #7626
|
|
|
Boshen
pushed a commit
that referenced
this issue
Dec 3, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Following from #7151, there are a few changes left to complete for parity with reacts lint rule:
useCallback
ident, not the second arg fix(linter): react/exhaustive-deps update span for unknown deps diagnostic #7249In the below case, we need to mark
props
as a dependency because it has athis
value. #7615I think we can just ignore the below case. It will throw an error (JS error) if you try to execute it (
foo
is used before its declaration)Same as above case
currently
produces an error saying
props.foo.toString
should be a dep.this should be changed to say that
props.foo
should be a dep.The text was updated successfully, but these errors were encountered: