[5.4] Make date/datetime cast difference more explicit by removing time part. #16799
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.
Hi,
Currently, both
date
anddatetime
cast types are using the same casting method. However, this can lead to unexpected results when a UNIX timestamp or Carbon instance containing a time part is assigned to adate
attribute.date
attributes keep the time part when it is known, but after saving the model and refreshing it, the time part might be lost. Example:As the cast types explicitly include both
date
anddatetime
, I think a more consistent approach would be to always remove the time part fromdate
attributes.Kind regards,
Jarno