#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 Carlton Gibson):
Is this really a `Someday/Maybe`, rather than a `wontfix` as it stands?
No doubt we evolve the capabilities here but this doesn't look at all
actionable with the current design.
As per comment on #29700, I'd (currently/initially) favour pointing users
to subclassing `AutocompleteJsonView` and seeing what they come up with.
I suspect good ideas would come out of there...
--
Ticket URL: <https://code.djangoproject.com/ticket/29010#comment:11>
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.9a2185c95d7407665bd2e59f3531b41e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
