-
-
Notifications
You must be signed in to change notification settings - Fork 707
perf(linter): only check for call expr once in unicorn/no-array-method-this
#14641
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
perf(linter): only check for call expr once in unicorn/no-array-method-this
#14641
Conversation
How to use the Graphite Merge QueueAdd either label to this PR to merge it via the merge queue:
You must have a Graphite account in order to use the merge queue. Sign up using this link. An organization admin has enabled the Graphite Merge Queue in this repository. Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue. This stack of pull requests is managed by Graphite. Learn more about stacking. |
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.
Pull Request Overview
This PR optimizes the no_array_method_this_argument linter rule by performing the call expression type check once at the entry point instead of redundantly checking in each helper function.
- Moved the
CallExpressionpattern match from helper functions to therunmethod - Updated helper function signatures to accept
&CallExpressiondirectly instead of&AstNode - Added
CallExpressionto the import list
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
Merge activity
|
CodSpeed Performance ReportMerging #14641 will not alter performanceComparing Summary
Footnotes
|
…od-this` (#14641) Simple refactor to only do a single call expression check instead of two.
44bc4df to
58e17ae
Compare

Simple refactor to only do a single call expression check instead of two.