-
-
Notifications
You must be signed in to change notification settings - Fork 496
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
feat(linter): add jsx support for only-used-in-recursion #7120
feat(linter): add jsx support for only-used-in-recursion #7120
Conversation
Your org has enabled the Graphite merge queue for merging into mainAdd the label “0-merge” to the PR and Graphite will automatically add it to the merge queue when it’s ready to merge. Or use the label “hotfix” to add to the merge queue as a hot fix. You must have a Graphite account and log in to Graphite in order to use the merge queue. Sign up using this link. |
CodSpeed Performance ReportMerging #7120 will not alter performanceComparing Summary
|
ff8289f
to
9bbc8fd
Compare
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 awesome, thank you! i will review properly later
This looks good to me i think we can re-use a few exising fns that are already |
@camc314 Thank you for the review. I’ve made the suggested changes. I'll rebase fix-up commit after this PR gets approval. |
I went ahead and sent an explicit review request, but no rush—take your time! :) |
14aa74c
to
90791de
Compare
90791de
to
23a0533
Compare
This comment was marked as resolved.
This comment was marked as resolved.
23a0533
to
14aa74c
Compare
14aa74c
to
f791c81
Compare
f791c81
to
bb2dabf
Compare
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.
thank you for contributing!
Co-authored-by: Cam McHenry <[email protected]>
Co-authored-by: Cam McHenry <[email protected]>
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 for your contribution!
aa4878c
to
c42d5ed
Compare
## [0.11.1] - 2024-11-09 ### Features - 4dd9b60 editor/vscode: Replace existing output channel and trace output channel with a single LogOutputChannel (#7196) (Nicholas Rayburn) - 1fcd709 linter: Add jsx support for only-used-in-recursion (#7120) (no-yan) - 4d577cf linter: Add `import/first` rule (#7180) (Dmitry Zakharov) - 9b8973f linter: Add `import/unambiguous` rule (#7187) (Dmitry Zakharov) - 5ab1ff6 linter: Implement @typescript-eslint/no-unsafe-function-type (#6989) (Orenbek) ### Bug Fixes - eea8879 editor/vscode: Update language client id to fix the resolution of the oxc.trace.server setting (#7181) (Nicholas Rayburn) - b73cfd9 linter: Fix `is_method_call` with parentheses and chain expression (#7095) (tbashiyy) ### Refactor - 8c0a362 linter: Use `ctx.source_range(comment.content_span())` API (#7155) (Boshen) - c5485ae semantic: Add `ancestor_kinds` iterator function (#7217) (camchenry) - abf1602 semantic: Rename `iter_parents` to `ancestors` (#7216) (camchenry) - 42171eb semantic: Rename `ancestors` to `ancestor_ids` (#7215) (camchenry) Co-authored-by: Boshen <[email protected]>
@no-yan great work! |
close #5530
This PR adds support for handling recursive JSX components, allowing detect functions like the one below:
Some logic is duplicated with the non-JSX case. But the refactor will be complicated and affects over-all, so we can make it in another PR.
cc: @DonIsaac @camc314