#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:12 Johannes Hoppe]:
> Is there a ticket now for the `limit_choices_to` issue yet? I'd really
like to fix that one.
I can create a ticket, but isn't it the same problem as this ticket? Once
the AutocompleteView knows which model to get "limit_choices_to" from, the
original issue being presented here would *also* be addressed at the same
time - unless I'm missing something?
I'll gladly create a separate ticket for limit_choices_to if you prefer, I
just thought that the solution to that problem would end up fixing this
issue as well...
--
Ticket URL: <https://code.djangoproject.com/ticket/29010#comment:13>
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.e91f793ae7be79e00923a761959d3c7f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
