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
I was wondering if you would be open for a possibility to allow complex lookups for the user model.
My proposal would be to allow another setting (e.g. CUSTOM_LOOKUP which is passed to get_or_create_user and would replace user_lookup_key and user_lookup_value if set.
My use case is that i have an ID field which isn't necessary defined and i want to provide a "fallback" field by using a query like Q(my_id="uid") | Q(email)="mail".
The text was updated successfully, but these errors were encountered:
I was wondering if you would be open for a possibility to allow complex lookups for the user model.
My proposal would be to allow another setting (e.g.
CUSTOM_LOOKUP
which is passed toget_or_create_user
and would replaceuser_lookup_key
anduser_lookup_value
if set.My use case is that i have an ID field which isn't necessary defined and i want to provide a "fallback" field by using a query like
Q(my_id="uid") | Q(email)="mail"
.The text was updated successfully, but these errors were encountered: