#29010: Allow customizing the autocomplete search results based on the querying
model
-------------------------------------+-------------------------------------
Reporter: Muslu Y. | Owner: nobody
Type: New feature | Status: new
Component: contrib.admin | Version: 2.0
Severity: Normal | Resolution:
Keywords: ForeignKey, | Triage Stage:
get_search_results, search_fields | Someday/Maybe
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by David W. Lloyd):
Replying to [comment:14 Johannes Hoppe]:
> Well not necessarily. I did have a go at this yesterday evening.
`limit_choices_to` could be fixed, without a larger refactoring.
> I would use a couple of strange API's though. I am not yet happy with my
solution.
I'm curious how limit_choices_to can be accessed without also then knowing
the referring model... so I'll log the ticket and link this one :)
--
Ticket URL: <https://code.djangoproject.com/ticket/29010#comment:15>
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/071.f024dae32eb6d9e824e739c6af557734%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
