Feature/allow ominiauth_success json override

README.md

@@ -729,6 +729,24 @@ mount_devise_token_auth_for 'User', at: 'auth', controllers: {
 }
 ~~~
 
+## Overriding the Omniauth Success resource serializer
+
+Rendering an Omniauth success works a litte differently to the other controllers which is why there is no render override. Instead we provide a method to override how you want the resource (usually the user object) to be serialized. The default is:
+
+~~~ruby
+def serialize_omniauth_success_resource(resource)
+  resource.as_json
+end
+~~~
+
+But you may not want to use the built in `as_json`. In which case, you can override it like this, for example:
+
+~~~ruby
+def serialize_omniauth_success_resource(resource)
+  MyCustomSerializer.new(resource).return_a_hash
+end
+~~~
+
 **Note:** Controller overrides must implement the expected actions of the controllers that they replace.
 
 ## Passing blocks to Controllers

app/controllers/devise_token_auth/omniauth_callbacks_controller.rb

@@ -42,7 +42,7 @@ def omniauth_success
 
       yield @resource if block_given?
 
-      render_data_or_redirect('deliverCredentials', @auth_params.as_json, @resource.as_json)
+      render_data_or_redirect('deliverCredentials', @auth_params.as_json, serialize_omniauth_success_resource(@resource))
     end
 
     def omniauth_failure
@@ -52,6 +52,11 @@ def omniauth_failure
 
     protected
 
+    #override this method to provide your own serialization strategy
+    def serialize_omniauth_success_resource(resource)
+      resource.as_json
+    end
+
     # this will be determined differently depending on the action that calls
     # it. redirect_callbacks is called upon returning from successful omniauth
     # authentication, and the target params live in an omniauth-specific