Fix unknown field error in ModelSerializer #9019
Merged
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.
My real scenario is when I include some fields that does not exists in the model. For example assume that I have a model called
Store
, which does not havetoken
field.In this example, if I have a
ModelSerializer
like this:Then I will face an exception like:
'Field name `token` is not valid for model `Store`.'
.This can really be a headache, when I have multiple serializers for
Store
model. So I suggest to simply have the model path, to be more clear about which serializer is corrupt.