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.
fix(eslint-factory): withhold prefer-structured-clone suggestion when the cloned value carries function properties #50846
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(eslint-factory): withhold prefer-structured-clone suggestion when the cloned value carries function properties #50846
Changes from all commits
bc73c9767b53f5917b3d5File filter
Filter by extension
Conversations
Uh oh!
There was an error while loading. Please reload this page.
Jump to
Uh oh!
There was an error while loading. Please reload this page.
There are no files selected for viewing
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.
[/tdd] The guard at
prefer-structured-clone.ts:119only suppresses suggestions whenclonedExpressionis anIdentifier— non-identifier expressions (e.g.JSON.parse(JSON.stringify(obj.sub))) always get the suggestion. A test pinning this boundary would prevent a future regression if the guard logic is widened.💡 Suggested test case to add inside this `it` block
@copilot please address this.
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.
[/diagnosing-bugs] The
AssignmentExpressionvisitor only detects direct identifier targets (x.prop = () => {}). Aliased or destructured parameters likeconst t = tool; t.handler = () => {}bypass the guard. This is an inherent heuristic limitation — consider adding a code comment acknowledging it so future contributors don't try to "fix" the check into something more complex than the risk warrants.💡 Suggested comment
@copilot please address this.
Uh oh!
There was an error while loading. Please reload this page.