Migrating from django_social_auth

[devangmundhra]

Since django_social_auth is going to be deprecated in favor of this library, is there a way to migrate pre-existing apps to this library without losing any functionality.
For example, there was support for pipelines and view decorators (dsa_view) which I didn't find in the code (I might have not looked in the correct place).
Also, will the social_auth tables need to be dropped and recreated if moving the django project to this library?

Thanks!

[juanriaza]

@devangmundhra Porting from django-social-auth

[devangmundhra]

Thanks! And can we still use the view decorators?

@dsa_view() 
def register_by_access_token(request, backend, *args, **kwargs):

[omab]

@devangmundhra, no, you need the @strategy decorator now (from social.apps.django_app.utils import strategy)

[omab]

@devangmundhra, there's no tables rename, but you might need to run a syncdb and delete the social_auth content type from the content-types table.

Pipelines are now stored on social.pipeline, there are a few extra ones, but the names are mostly the same, check the default setting here http://psa.matiasaguirre.net/docs/pipeline.html#authentication-pipeline. If you happen to have custom pipelines, the parameters are the same, plus the strategy in case you need it. Partial pipelines still work but the save_status_to_session is located at social.pipeline.partial now, there's also a decorator @partial in that same module that can be used instead of save_status_to_session, it's cleaner that way.

Setting names must be prefixed with SOCIAL_AUTH_, some backends were renamed a little (not the popular ones like Google, Facebook and Twitter).