Allow custom serializer class for request and response #8526
Conversation
This file contains hidden or 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
|
Hi @Smixi I just saw your commit, I feel like we need the same things at the same time because I rebased with master too a few days ago! Feel free to close this PR and participate in the discussion on the other one :) |
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.
Description
This is a rerun of the CI of khamaileon's commit (#8347) because of an error with mkdoc and jinja at the time (mkdocs/mkdocs#2799). If I remember correctly, the OpenApi schema part is already there in this commit 8812394 but the handler for generics views in the generic.py was missing. No change from previous commit otherwise than merging with a recent master branch.
CI: https://github.com/Smixi/django-rest-framework/actions/runs/2492005353
The feature allow to define different serializers for input/output in generic views, and integrate with schema spec generation for such usecase.
I don't know how to properly push into an already created PR (if it is possible ?), if that's not the way to do it then close this :/.