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
The default Django user model has first_name and last_name fields, which is bad for internationalisation -- bad enough that I'd consider this a bug.
We're already using a custom user model, so we should update this to use a full_name field instead. That's a more substantial change from the defaults than our current custom user model, but the changes are mostly mechanical and really just a matter of copying the AbstractUser base class from django.contrib.auth.models, changing the fields it has and changing our user model to derive from it (or just folding the new "abstract user" definition into our user model.
These changes then need to propagate through the API and to the front end as well, obviously.
The text was updated successfully, but these errors were encountered:
The default Django user model has
first_name
andlast_name
fields, which is bad for internationalisation -- bad enough that I'd consider this a bug.We're already using a custom user model, so we should update this to use a
full_name
field instead. That's a more substantial change from the defaults than our current custom user model, but the changes are mostly mechanical and really just a matter of copying theAbstractUser
base class fromdjango.contrib.auth.models
, changing the fields it has and changing our user model to derive from it (or just folding the new "abstract user" definition into our user model.These changes then need to propagate through the API and to the front end as well, obviously.
The text was updated successfully, but these errors were encountered: