[Serializer] Trigger deprecation when could not parse date with default format #58966
Conversation
|
@nicolas-grekas Could you have a look? |
src/Symfony/Component/Serializer/Normalizer/DateTimeNormalizer.php
Outdated
Show resolved
Hide resolved
….php Co-authored-by: Mathias Arlaud <mathias.arlaud@gmail.com>
|
Looks like the tests must be updated to not trigger the deprecation. |
| @@ -126,6 +126,8 @@ public function denormalize(mixed $data, string $type, ?string $format = null, a | |||
| if (false !== $object = $type::createFromFormat($defaultDateTimeFormat, $data, $timezone)) { | |||
| return $object; | |||
| } | |||
|
|
|||
| trigger_deprecation('symfony/serializer', '7.3', \sprintf('A "%s" will be thrown when a date could not be parsed using the default format "%s".', NotNormalizableValueException::class, $defaultDateTimeFormat)); | |||
There was a problem hiding this comment.
I think we should trigger a deprecation here only if the fallback manages to instantiate it. The case where the fallback throws an exception (already turned into a NotNormalizableValueException below) should not trigger a deprecation.
There was a problem hiding this comment.
As I understand, in 8.0, the fallback should be removed, right?
There was a problem hiding this comment.
yes. And that's my point: if the fallback also fails, you already have the same behavior than what would happen in 8.0 and we should not trigger a deprecation in that case as the behavior will not change. Try submitting foobar as value to reproduce that case.
There was a problem hiding this comment.
I have rechecked and now realise that fallback should not be removed in 8.0. Fallback should still be used when datetime_format is set to null.
66a1ede to
663eec5
Compare
|
@mtarld I have done with your comments. |
Relates to #43329 (comment)