Repository navigation
[Arguments] Deprecate RemoveMethodCallParamRector as too niche and generic - #8766
Merged
Merged
Conversation
TomasVotruba
enabled auto-merge (squash)
October 22, 2026 09:52
TomasVotruba
disabled auto-merge
October 22, 2026 09:54
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
1 participant
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.
Removing a single positional method-call param by object type + method name is too generic: the object-type match fires on any caller with a same-named method, so it can strip arguments from unrelated calls and produce invalid code. Prefer a dedicated rule for the specific API change.
Deprecates the rule following the standard pattern:
implements DeprecatedInterface+@deprecatednote,refactor()throwsRemoveMethodCallParamvalue object (only this rule used it)