#5833: [newforms-admin] Custom FilterSpecs
-------------------------------------------+--------------------------------
Reporter: Honza_Kral | Owner: jkocherhans
Status: assigned | Milestone:
Component: django.contrib.admin | Version: SVN
Resolution: | Keywords: nfa-someday
list_filter filterspec nfa-changelist ep2008
Stage: Accepted | Has_patch: 1
Needs_docs: 0 | Needs_tests: 1
Needs_better_patch: 0 |
-------------------------------------------+--------------------------------
Changes (by [email protected]):
* cc: [email protected] (added)
* needs_better_patch: 1 => 0
* needs_tests: 0 => 1
* stage: Design decision needed => Accepted
Comment:
I am attaching a new patch against the latest HEAD. It's based on
gerdemb's patch but now allows for consuming of GET parameters to allow
for custom, non-field based querystring keys. The patch also implements a
priority queue in a sense; FieldFilterSpec.register() allows you to pass
in high_priority=True in order to register the FieldFilterSpec as high
priority. This argument is True by default but passed in as False for all
default filter specs. High priority specs are inserted before normal
priority specs, but order is preserved amongst the two separate groups.
Let me know what you think of that solution.
I'm also moving this to Accepted since it's on the 1.1 features list
(forgive me if this is an incorrect decision). Also flagging it as Needs
tests.
--
Ticket URL: <http://code.djangoproject.com/ticket/5833#comment:31>
Django <http://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 post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
