I second this; I would have moved to having auth.User be abstract, and force
projects to create their own _always_, except (a) it breaks a lot of history,
and (b) it breaks the "ready to go out of the box" nature.
It's a small cost at the start of your project, that avoids problems for a
sizabl
I can see where you might think that, but I actually believe it should
go in the other direction - that the User model should be the absolute
_minimum_ of an entity.
1. The User model is retrieved with every authenticated request. The
more fields in the model, the more data is being handled un
No they should not!
Django provides an easy way to extend (or replace) the built-in User model.
There are far too many fields people might want to add and it would be a
complete mess, if we would fulfill all of these requests.
Please refer to the docs
at
https://docs.djangoproject.com/en/3.1/t
Hey Developers! Some fields should be inside models.User e.g. image,
phone_number. Some developers don't want to extend the auth model. Yes i
know there are some ways to extends the auth model. But i think these
fields should come with models.User
--
You received this message because you are s
