3 ms·
As someone who works in Django a lot, their non-standard approach to defining models is wild. ie. Their approach in accounts models.py: https://github.com/sa
by agconti 6y ago
As someone who works in Django a lot, their non-standard approach to defining models is wild.
ie.
Their approach in accounts models.py:
https://github.com/saasitive/django-react-boilerplate/blob/main/backend/server/apps/accounts/models.py https://github.com/saasitive/django-react-boilerplate/blob/m...
Over the standard approach in their notes models.py:
https://github.com/saasitive/django-react-boilerplate/blob/main/backend/server/apps/notes/models.py https://github.com/saasitive/django-react-boilerplate/blob/m...
- pplonski86 6y agoThe tutorial is still under the development and I will update the User model logic for sure (for payments and teams features). The 'wild' overwrite of User model was minimal to set email as required field in User model.
- wbc 6y agoWhat are your thoughts on AbstractUser https://docs.djangoproject.com/en/3.1/topics/auth/customizing/#using-a-custom-user-model-when-starting-a-project https://docs.djangoproject.com/en/3.1/topics/auth/customizin...?
- disgrunt 6y agoDjango now just recommends a custom user model if you intend to change it. In my experience, this is now a best practice in Django. [0] [0]: https://docs.djangoproject.com/en/3.1/topics/auth/customizing/#auth-custom-user https://docs.djangoproject.com/en/3.1/topics/auth/customizin...