Repository navigation
[Transform] Deprecate ArrayDimFetchToMethodCallRector as too niche and able to create invalid calls - #8762
Merged
TomasVotruba merged 2 commits intoOct 22, 2026
Conversation
…d able to create invalid calls
TomasVotruba
deleted the
worktree-deprecate-array-dim-fetch-to-method-call
branch
October 22, 2026 08:31
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
2 participants
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.
This rule is too niche, never used in practice, and can produce invalid method calls on objects that lack the configured
get/set/has/unsetmethods.Use a specific, targeted rule instead.
Rule is gutted to throw on
refactor()and marked@deprecated+DeprecatedInterface, following the existing deprecation pattern. Its tests, config value object, and enum are removed.