#24947: Move admin changelist filters into a separate class (Mixin)
-------------------------------+-------------------------------------
Reporter: nanuxbe | Owner: nanuxbe
Type: New feature | Status: new
Component: contrib.admin | Version: master
Severity: Normal | Keywords: admin changelist filter
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+-------------------------------------
As suggested by @mjtamlyn at DjangoConEurope, move admin changelist
filters into a separate class, so that it is usable both by the admin and
CBV's.
I am thinking of creating first 2, then 3 mixins:
- a BaseListFilter mixin holding most of the logic of filtering
- an AdminFilter mixin (extending BaseListFilter) with admin changelist
specifics
- finally a FilteredList Mixin (extending BaseListFilter) to use with
CBV's
--
Ticket URL: <https://code.djangoproject.com/ticket/24947>
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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/050.22d7fd8790c250b6b4f1ec7721d40d07%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
