Fix EntityPatchRector and newExpr rector issues #351
Merged
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
This PR fixes two bugs reported in #350:
Bug 1: EntityPatchRector was overly broad
->set([array])to->patch([array])without checking object typeCake\ORM\EntityinstancesObjectTypecheck andisInstanceOf(Entity::class)validationBug 2: newExpr()->count() pattern not handled correctly
$query->newExpr()->count()was being transformed to$query->expr()->count()which is invalid$query->func()->count('*')since it's creating aggregate functionsNewExprToFuncRectorthat runs before the general newExpr → expr renameTest plan
Related Issues
Fixes #350
🤖 Generated with Claude Code