#774 Do not re-use serializers for CompatibleFieldSerializer and TaggedFieldSerializer #788
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.
Resolves #774
Resolves #784
This PR prevents re-using
ReflectField
serializers when usingCompatibleFieldSerializer
andTaggedFieldSerializer
.Re-using serializers works for
FieldSerializer
because it only provides a concretevalueClass
for final field types or iffixedFieldTypes
is enabled.CompatibleFieldSerializer
andTaggedFieldSerializer
always populate thevalueClass
with the last value they encounter.I'm not fond of this solution but it is the only way to resolve this issue without breaking backwards compatibility.