-
-
Notifications
You must be signed in to change notification settings - Fork 475
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
fix(useHookAtTopLevel): recognize hook property in member expression calls #3140
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
github-actions
bot
added
A-Linter
Area: linter
L-JavaScript
Language: JavaScript and super languages
A-Changelog
Area: changelog
labels
Jun 9, 2024
ematipico
approved these changes
Jun 10, 2024
arendjr
approved these changes
Jun 10, 2024
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.
Thanks!
arendjr
changed the title
fix(use-hook-at-top-level): recognize hook property in member expression calls
fix(useHookAtTopLevel): recognize hook property in member expression calls
Jun 10, 2024
CodSpeed Performance ReportMerging #3140 will not alter performanceComparing Summary
|
Started to get false-positives: beforeEach(() => jest.useFakeTimers('legacy'));
afterEach(() => jest.useRealTimers()); |
Can you open a new issue? |
Yes, sure: #3337 |
This was referenced Aug 28, 2024
This was referenced Sep 9, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
A-Changelog
Area: changelog
A-Linter
Area: linter
L-JavaScript
Language: JavaScript and super languages
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
this is needed for parity with eslint-plugin-react-hooks. specifically when using hook APIs like trpc or simply React.useEffect instead of useEffect, the current lint rule will fail to catch rules-of-hooks violations.
Test Plan
updated test case