#9025: Nested Inline Support in Admin
-------------------------------+------------------------------------
Reporter: pixelcort | Owner:
Type: New feature | Status: new
Component: contrib.admin | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 1 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 1
-------------------------------+------------------------------------
Changes (by Gargamel):
* status: assigned => new
* owner: Gargamel =>
Comment:
Well, I'm going to unassign this, because I don't feel I'm progressing
fast enough... I'm still gonna work on it in my spare time, but with a
different approach. I just can't wrap my head around the patterns used for
the InlineFormSet classes and such, and this is definitely holding me
down.
On the other hand, maybe my current approach is just completely wrong...
I'm just gonna take my time to really understand the codebase behind the
whole inlines and then try again until I succeed.
Well, if anybody really wants nested inlines, the supplied patch works ok
I guess, except for some special cases so that will have to do for now.
--
Ticket URL: <https://code.djangoproject.com/ticket/9025#comment:139>
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 https://groups.google.com/groups/opt_out.
