#7028: Better raw_id_fields feedback in newform-admins branch
-------------------------------------+-------------------------------------
Reporter: Marcob | Owner: nobody
<marcoberi@…> | Status: new
Type: New feature | Version: master
Component: contrib.admin | Resolution:
Severity: Normal | Triage Stage: Accepted
Keywords: raw-id-fields nfa- | Needs documentation: 0
someday design_ux | Patch needs improvement: 1
Has patch: 1 | UI/UX: 1
Needs tests: 1 |
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Comment (by julien):
I've worked on a reasonably straightforward implementation (1) for this
inspired from DrMeers' "cooked_ids" (2). I've also written a number of
selenium tests. It has the advantage of preserving raw_id_fields if you
still want them (for whatever reason), while allowing you to use the more
user-friendly version (here called "token_fields").
The main piece that's still missing from this implementation is the
ability to work with non-integer primary keys.
Any feedback?
(1) https://bitbucket.org/drmeers/django-
generic/src/bd20113dce83a5ba6db30a96f0493b93e3aeea17/generic/admin/mixins/cooking.py
(2)
https://github.com/jphalip/django/compare/django:04489c7dbf8f69de84ca272a0a1710e7b6067e9d...ticket-7028
-token-fields
--
Ticket URL: <https://code.djangoproject.com/ticket/7028#comment:74>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/086.3d03aad8050821d62950559c772ffddd%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.
