Skip to content

Support for separate serializers for request and response payloads #162

@phantran

Description

@phantran

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions