[Transform] Fixes for ArrayDimFetchToMethodCallRector #5727
Conversation
This file contains 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
samsonasik
approved these changes
Mar 16, 2024
|
Thank you @peterfox |
samsonasik
reviewed
Mar 16, 2024
|
|
||
| foreach ($this->arrayDimFetchToMethodCalls as $arrayDimFetchToMethodCall) { | ||
| if (! $this->isObjectType($node->var, new ObjectType($arrayDimFetchToMethodCall->getClass()))) { |
There was a problem hiding this comment.
@peterfox this can be improved, by move new ObjectType() in the configuration itself, so just call instead of re-create object, eg:
-new ArrayDimFetchToMethodCall('SomeClass', 'make')
+new ArrayDimFetchToMethodCall(new ObjectType('SomeClass'), 'make')so only define ObjectType() once in the config ;), like what ArgumentAdderRector do:
rector-src/rules/Arguments/Rector/ClassMethod/ArgumentAdderRector.php
Lines 86 to 93 in d9b64c7
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.
Fixes for rule introduced in #5723 per @samsonasik feedback