#17985: Add additional lookup_allowed whitelist functionality to ModelAdmin
-------------------------------+--------------------------------------
     Reporter:  3point2        |                    Owner:  nobody
         Type:  New feature    |                   Status:  reopened
    Component:  contrib.admin  |                  Version:  1.4
     Severity:  Normal         |               Resolution:
     Keywords:                 |             Triage Stage:  Unreviewed
    Has patch:  0              |      Needs documentation:  0
  Needs tests:  0              |  Patch needs improvement:  0
Easy pickings:  0              |                    UI/UX:  0
-------------------------------+--------------------------------------
Changes (by 3point2):

 * status:  closed => reopened
 * resolution:  wontfix =>


Comment:

 Sorry to re-open. I'm fine with overriding lookup_allowed, but I opened
 this ticket because I feel like this is a feature that is generally
 useful, and lookup_allowed is undocumented. I feel like this functionality
 should be officially supported, and overriding an undocumented method is
 more of a work-around. Also see http://www.hoboes.com/Mimsy/hacks/fixing-
 django-124s-suspiciousoperation-filtering/lookup_allowed-gets-new-
 parameter-value/

 At the very least, documenting lookup_allowed would be helpful.

 If on the other hand you feel that this functionality is not a common use
 case, I'm fine with closing the ticket and sticking with the work around.

-- 
Ticket URL: <https://code.djangoproject.com/ticket/17985#comment:2>
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Reply via email to