-
Notifications
You must be signed in to change notification settings - Fork 39
Nested serializer fields aren't described in the request body #113
Comments
I prepared code fixing (presumably) this issue. You can test it by installing |
That's great news, I'll give it a try |
Thanks for looking into this unfortunately it doesn't seem to be working for me. I used the serializer below as the request_serializer and response_serializer and got the following JSON SERIALIZER
REQUEST
RESPONSE
|
Unfortunately i've not tested serializers with more than one nesting level. I made an update for handling this and put it in same branch. Some features / bugs of updated solution:
Example view and serializer:
Request example
Response example
|
Fantastic! Works really well. Thanks you so much! |
I updated the code, new features is:
request example
and serializer:
i push in same branch because this feature set depends on original issue (nested field inspections) |
Description
If main serializer has any nested serializers except ListSerializer (it's handled correctly), fields of this sub-serializers doesn't shown on html page with api description.
What I Did
Main serializer is
CheckDocRequestSerializer
and in this case fieldsdoc_type
,number
will be shown forDocumentSerializer
butPersonSerializer
will be described asobject
without any sub-elements."Request example":
The text was updated successfully, but these errors were encountered: