refactor(linter): simplify no-param-reassign using MemberWriteTarget flag#21206
Merged
graphite-app[bot] merged 1 commit intomainfrom Apr 13, 2026
Merged
Conversation
Member
Author
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. |
3 tasks
Merging this PR will not alter performance
Comparing Footnotes
|
a56bb73 to
327c2a5
Compare
854aba9 to
fc3807a
Compare
327c2a5 to
deb7c6d
Compare
fc3807a to
27f6843
Compare
2 tasks
deb7c6d to
327c2a5
Compare
27f6843 to
3f3268f
Compare
327c2a5 to
20c48c5
Compare
3f3268f to
e205db9
Compare
Member
Author
|
Pure refactor |
e205db9 to
60463f2
Compare
20c48c5 to
30c2301
Compare
60463f2 to
006c9be
Compare
30c2301 to
3560adb
Compare
006c9be to
428d19e
Compare
3560adb to
6dd061c
Compare
428d19e to
bc7e404
Compare
Contributor
Merge activity
|
…et` flag (#21206) ## Summary - Replace the 97-line `is_modifying_property()` ancestor-walking function with a single `reference.flags().is_member_write_target()` check - Now that `MemberWriteTarget` covers all property modification patterns (simple `=`, compound `+=`, update `++/--`, `delete`), the manual ancestor walk is no longer needed Depends on #21205. ## Test plan - [x] Existing `no-param-reassign` tests pass unchanged - [x] `just ready` passes 🤖 Generated with [Claude Code](https://claude.com/claude-code)
bc7e404 to
4cf38dd
Compare
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
is_modifying_property()ancestor-walking function with a singlereference.flags().is_member_write_target()checkMemberWriteTargetcovers all property modification patterns (simple=, compound+=, update++/--,delete), the manual ancestor walk is no longer neededDepends on #21205.
Test plan
no-param-reassigntests pass unchangedjust readypasses🤖 Generated with Claude Code