#25142: Refactor access mixins to allow customisation
--------------------------------------+------------------------------------
Reporter: dfunckt | Owner: dfunckt
Type: Cleanup/optimization | Status: assigned
Component: contrib.auth | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 1
Needs tests: 1 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
--------------------------------------+------------------------------------
Comment (by dfunckt):
The point is to allow extensibility, indeed -- my comment was more about
asking for a decision to be made, placing a couple counter arguments along
the way. Hadn't see that AccessMixin was already documented, so I think
that also documenting has_permission is the way to go. I will update the
PR later.
--
Ticket URL: <https://code.djangoproject.com/ticket/25142#comment:12>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/065.ffe590695909acd4f00e00cbcf39ec92%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
