This repository has been archived by the owner on Jan 11, 2021. It is now read-only.
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.
Another one I needed - support for Arrays.
DRS doesn't make any attempt at the moment to discern if a view returns an array of Serializer objects. This is problematic when used with
swagger-codegen
, as APIs which are supposed to return lists of objects don't say that they do, and codegen expects a single object response.I did see a similar PR #404, but this has been open for several months with no activity and I needed this for my own purposes now.
What this PR does that the other does not, is push inspection into the introspection layer. In addition, viewset methods named
list
are automatically made into array responses (as they always are with DRF). I've taken the concept of applying 'many' to the YAML docstring stanza as well, to allow FBVs and other detail / list routes in viewsets to work.I've also added an expanded information section in
misc.rst
, with cross-referenced expansion on themany
yaml attribute inyaml.rst
.Any questions, give me a shout.