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
Hi, I've implemented a social auth layer using django-social-auth for this open source project: hasadna/openmuni-budgets#405
It includes several custom changes:
-create user was changed, we use a custom user model that inherits from Django's abstract user class.
-A strict unique email constraint was implemented, meaning that user can only add social accounts that have the same email as his account, or in case of registration using a social account, all additional accounts added must comply with the strict-identical email restriction.
Question is, how complicated should it be to migrate to the new library?.
The main reason that we are considering to migrate to the new library is the fact that t has a really high test coverage, and from there ,implementing test for our custom use cases should be really easy.
The down side is that we are an open source project, without resources, and without much time at our disposal.
I am opening this issue for other django-social-auth users as well, as there is not documentation \ guide available that covers migrating from django-social-auth to python-social-auth.
Thanks a lot!,
Oleg.
The text was updated successfully, but these errors were encountered:
Hi, I've implemented a social auth layer using django-social-auth for this open source project:
hasadna/openmuni-budgets#405
It includes several custom changes:
-create user was changed, we use a custom user model that inherits from Django's abstract user class.
-A strict unique email constraint was implemented, meaning that user can only add social accounts that have the same email as his account, or in case of registration using a social account, all additional accounts added must comply with the strict-identical email restriction.
Question is, how complicated should it be to migrate to the new library?.
The main reason that we are considering to migrate to the new library is the fact that t has a really high test coverage, and from there ,implementing test for our custom use cases should be really easy.
The down side is that we are an open source project, without resources, and without much time at our disposal.
I am opening this issue for other django-social-auth users as well, as there is not documentation \ guide available that covers migrating from django-social-auth to python-social-auth.
Thanks a lot!,
Oleg.
The text was updated successfully, but these errors were encountered: