fix: handle DateTime, arrays, and nulls properly in value comparison #12066
+74
−1
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.
Patch Summary
This patch improves the value comparison logic in Doctrine’s
UnitOfWorkclass during change detection.Key Changes
Introduces a private method
valuesAreEqual()that compares values with special handling for:nullvalues,DateTimeInterfaceinstances using the spaceship operator (<=>),===) for other types.Replaces existing strict equality checks with
valuesAreEqual()to prevent false positives.Benefit
Enhances reliability in detecting changes for entities with
DateTimeand array fields.