Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for separate serializers for request and response payloads #162

Open
phantran opened this issue Apr 4, 2023 · 0 comments
Open

Comments

@phantran
Copy link

phantran commented Apr 4, 2023

Currently, the code only supports using one serializer for a view. However, in some cases, the schema of the request payload may be different from the schema of the response payload.

This can lead to problems where the serializer used for the request payload does not properly deserialize the data in the response payload, or where the serializer used for the response payload does not properly serialize the data in the request payload.

To address this issue, we need support for using separate serializers for the request and response payloads in views. This would allow us to ensure that the data is properly serialized and deserialized in both directions, even when the schemas of the request and response payloads are different.

Possible solutions might include adding a new optional serializer called response_serializer to AbstractBaseAPI

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant