rest-auth responses

[jayvdb]

Likely rest-auth will be full of oddities, because it is highly configurable, and also it interfaces with other highly configurable apps.

Note there is a very serious fork at https://github.com/jazzband/dj-rest-auth - I expect we and many ppl will switch soon, and I am also expecting there to be a lot of similarities, so many of fixers will likely be common, but in this case (unlike drf-jwt), the package module name was modified.

Excerpt below for one fixer.

Note UserSerializer in it isnt included as mine is local in the same file - that would be another fetch from a settings module.

from django.conf import settings as global_settings

from allauth.account import app_settings as allauth_settings

from rest_auth.serializers import JWTSerializer, TokenSerializer

from rest_framework import serializers


class SignupResponseSerializer(serializers.Serializer):
    if allauth_settings.EMAIL_VERIFICATION == \
                allauth_settings.EmailVerificationMethod.MANDATORY:
        detail = serializers.CharField(read_only=True, required=False)
    else:
        user = UserSerializer(read_only=True)
        if getattr(global_settings, 'REST_USE_JWT', False):
            token = JWTSerializer(read_only=True)
        else:
            token = TokenSerializer(read_only=True)

class OpenAPI_Fix_RestAuth_Registration(OpenApiViewExtension):
    target_class = 'rest_auth.registration.views.RegisterView'

    def view_replacement(self):

        class Fixed(self.target_class):

            @extend_schema(
                responses=SignupResponseSerializer,
            )
            def post(self, request, *args, **kwargs):
                pass

        return Fixed

[jayvdb]

#119 is relevant here, as the detail field used throughout rest-auth is "piggy-backing" on the DRF core default response structure.

[jayvdb]

rest_auth.views.LogoutView and rest_auth.registration.views.VerifyEmailView also both have responses of only the DRF core default response field detail.

LoginView has a method get_response_serializer, which returns JWTSerializer or TokenSerializer, similar to RegisterView/SignupResponseSerializer above. That method only exists on that one class.
However it is copied a lot. If generically supported, we'd need to be careful as that name is also used (slightly differently) by other apps such as drf-crud-proxy.