[Serializer] Fix BackedEnumNormalizer behavior with partial denormalization #62321
+83
−11
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.
This PR fixes a bug in
BackedEnumNormalizerthat occurs when usingcollect_denormalization_errorsandallow_invalid_valuesat the same time.When
allow_invalid_valueswas set, the normalizer would returnnullfor invalid data (likenull) beforeNotNormalizableValueExceptioncould be thrown.This caused the denormalization to fail with a fatal
TypeError(e.g.,Typed property ... must not be null) instead of populating aPartialDenormalizationExceptionwith the expected type errors.This fix ensures that
NotNormalizableValueExceptionis still thrown whencollect_denormalization_errorsis active (not_normalizable_value_exceptionscontext key is set), allowing the Serializer to catch it and report the error correctly.