From 38607cdc113cffd30c5e8b0cfd3d823e8457f620 Mon Sep 17 00:00:00 2001
From: Philippe Luickx <philippe.luickx@gmail.com>
Date: Tue, 14 Apr 2015 13:10:53 +0300
Subject: [PATCH] now I get why response_serializer is used...

---
 rest_auth/views.py | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/rest_auth/views.py b/rest_auth/views.py
index 33d93b1..b0ed213 100644
--- a/rest_auth/views.py
+++ b/rest_auth/views.py
@@ -43,7 +43,7 @@ class Login(GenericAPIView):
     authentication_classes = (EverybodyCanAuthentication,)
     serializer_class = LoginSerializer
     token_model = Token
-    token_serializer = TokenSerializer
+    response_serializer = TokenSerializer
     user_serializer = UserDetailsSerializer
 
     def login(self):
@@ -54,7 +54,7 @@ class Login(GenericAPIView):
             login(self.request, self.user)
 
     def get_response(self):
-        response = self.token_serializer(self.token).data
+        response = self.response_serializer(self.token).data
         user = self.user_serializer(instance=self.user).data
         response['user'] = user
         return Response(