#31355: Improving auth app
-------------------------------------+-------------------------------------
Reporter: Dima | Owner: nobody
Knivets |
Type: | Status: new
Cleanup/optimization |
Component: | Version: 3.0
contrib.auth |
Severity: Normal | Keywords: auth prototyping
Triage Stage: | Has patch: 0
Unreviewed |
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-------------------------------------+-------------------------------------
Since one of the philosophies of Django is quick development, we need to
do something about the auth app. At the moment, when a user starts a
project that requires auth features they have to do these things manually:
- build templates for each auth view (9 templates total)
- build a SignUp view from scratch since it is not provided by Django,
[https://docs.djangoproject.com/en/3.0/topics/auth/default/#using-the-
views unlike other auth views]
- create a custom user model (this is recommended by Django docs and a
user would likely want to be able to auth with email rather than username)
I've read that one of the reasons of not shipping the templates is that
you can't provide a template that will fit on every site. But that
reasoning is kind of missing the purpose. At a prototype stage, it doesn't
matter much how your reset password template looks like. You just want the
most basic functionality that works, so that you can focus on your custom
features and come back to polishing the look later.
The problems that I described can easily consume from 2 to 10 hours of dev
time (based on your familiarity with Django). These are the hours that
could've been spent on the actual application.
One of the major use cases of high level frameworks like Django is
prototyping. However, each element of friction, like the ones that I
described, reduce the appeal of Django as a great tool for prototyping.
--
Ticket URL: <https://code.djangoproject.com/ticket/31355>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/050.cae858679802a07b1bd95b6989f0f947%40djangoproject.com.