-
Notifications
You must be signed in to change notification settings - Fork 63
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Not the same behavior as Django's default User #23
Comments
Yes, that behaviour is different from Django's User model, but can be easily implemented as explained in https://github.com/jcugat/django-custom-user#extending-emailuser-model Maybe it could be a good idea to add another model to this package (let's say |
Personally, I think it's cleaner and less confusing if this app just provides a single model. Currently, the email replacing the username is just one of the differences. Would you be open to having the existing |
That is exactly what I'm looking for. Honestly, I can't believe there is not a package that does just that. There used to be, but it is no longer maintained, and doesn't support newer versions of Django. |
+1 |
I think having the first name and last name in the profile model rather than the user model makes more sense. It may take some additional effort moving it over initially but makes the project structure much cleaner:
|
This project's description is:
The thing is, this custom user model doesn't have the same behavior as Django's default User. I expected this to be exactly the same as what I get with
from django.contrib.auth.models import User
, only without a username. It turns out that it's missing thefirst_name
andlast_name
fields. Also, theget_full_name
andget_short_name
methods behave differently than Django's default User.I propose that these differences be brought into alignment with Django's default behavior. Either that or change this project's description so that it's not misleading. Other than that, this project is great!
The text was updated successfully, but these errors were encountered: