Implement dynamic field serialization on endpoints that lack it #314
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.
In order to fix #300, changed
CharClassSerializer
(as well as other serializers that do not currently support dynamic field serialization) to inherit fromDynamicFieldsModelSerializer
. Did so by creating an abstract base class calledDynamicFieldsHyperlinkedModelSerializer
(hate how long that name is, but it is technically the most correct name for it) that inherits from bothDynamicFieldsModelSerializer
andserializers.HyperlinkedModelSerializer
and modified all serializer classes that inherited from both of those classes individually, as well as all serializers that inherited from onlyserializers.HyperlinkedModelSerializer
to inherit from this new abstract class.As a part of this change, also modifed
DynamicFieldsModelSerializer
to use the lineinstead of
as the latter caused a bug when the
SubraceSerializer
inherited from the DFMS, asSubraceSerializer
can be called from withinRaceSerializer
, in which case therequest
key does not exist, and an error is thrown.