#14370: Adding support for Autocomplete in contrib.admin
-------------------------------------+-------------------------------------
Reporter: tyrion | Owner: nobody
Type: New feature | Status: new
Component: contrib.admin | Version: master
Severity: Normal | Resolution:
Keywords: autocomplete, | Triage Stage: Accepted
jquery, javascript, widgets, |
admin |
Has patch: 1 | Needs documentation: 1
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 1
-------------------------------------+-------------------------------------
Changes (by codingjoe):
* cc: info@… (added)
Comment:
I'm maintaining `django-select2` and wrote the current version. Let me
share my thoughts on integrating something similar in
`django.conrtib.admin`.
`django-select2` pickels the query and stores it in `django.core.cache`,
to work as a drop in widget. I think this would be a bit over the top. I
would suggest using `app_name`, `model_name` and `field_name` to uniquely
identify the relation.
From that point it should be possible to determine the queryset including
`limit_choices_to` constraints.
I think that `select2` is a great choice, I worked with other libraries,
but since `select2` version 4, I'd recommend it over other solutions.
If you want I could give it a shot. In any case feel free to use code from
`django-select2`.
--
Ticket URL: <https://code.djangoproject.com/ticket/14370#comment:37>
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/064.2295b0912b1b09491af3b63c302f5cc8%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
