You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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
The text was updated successfully, but these errors were encountered: