DRF==3.6.4, added explicit fields for some ModelSerializers - fixes #397 #399
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jeverling
force-pushed
the
397-upgrade-drf
branch
from
1cb92e9
to
abcb521
Compare
|
Fixes #397 |
18 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Django REST Framework 3.6 contains some fixes, for example using a
sourceparameter with a Serializer e.g.serializers.CharField(source='json.username', default=None, allow_null=True)fails gracefully with DRF 3.6 while it raises an exception with DRF 3.3.2.It is necessary to explicitly add
fields = '__all__'toModelSerializerinstances that neither setfieldsorexclude, but as far as I can tell that only applied toNoteSerializerandMetaDataSerializer.