#16226: [patch] prepopulated_fields only work with slug fields and break on non-
char fields
-------------------------------------+-------------------------------------
Reporter: | Owner: peter_kese
peter_kese | Status: new
Type: Bug | Component: contrib.admin
Milestone: | Severity: Normal
Version: SVN | Keywords:
Resolution: | Has patch: 1
Triage Stage: Design | Needs tests: 0
decision needed | Easy pickings: 0
Needs documentation: 0 |
Patch needs improvement: 0 |
UI/UX: 1 |
-------------------------------------+-------------------------------------
Changes (by aaugustin):
* stage: Unreviewed => Design decision needed
Comment:
Since the "wontfix" on #4509 was weak ("don't mind a wontfix") and a long
time ago, and interest for this issue has surfaced again, I'm marking this
as DDN in order to choose between:
* 1) By design, `prepopulated_fields` works only when the target is a
!SlugField => then it's a documentation issue, and #15922 must be marked
as "wontfix" too.
* 2) `prepopulated_fields` should work with any kind of field => then
there should be a discussion of how exactly it behaves with non-slug
fields, and this ticket is a good starting point.
If 2) is chosen, since prepopulating non-slug fields was neither
explicitly allowed or forbidden, it's difficult to say what is backwards
compatible and what isn't. We should try to limit the changes to the
current behavior, unless it's obviously buggy.
My advice of writing to django-developers still stands :)
--
Ticket URL: <https://code.djangoproject.com/ticket/16226#comment:5>
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
