#4656: Allow In-depth serialization by specifying depth to follow relationship
-------------------------------------+-------------------------------------
Reporter: | Owner: nobody
jay.m.martin@… | Status: new
Type: New | Component: Core
feature | (Serialization)
Milestone: | Severity: Normal
Version: | Keywords: feature
Resolution: | Has patch: 0
Triage Stage: Accepted | Needs tests: 0
Needs documentation: 0 | Easy pickings: 0
Patch needs improvement: 0 |
UI/UX: 0 |
-------------------------------------+-------------------------------------
Comment (by tomchristie):
There is some movement on this ATM.
I sprinted on the task at !DjangoCon.eu and made some progress, which Russ
broadly gave a thumbs up to.
If anyone's interested in helping out and finally making some progress on
this it'd be great if you could get in touch.
I've emailed the dev list with a rough proposal as it stands, and there's
an initial implementation, see here...
https://groups.google.com/d/topic/django-developers/H2EKZBsRlFY/discussion
There's certainly more work to do in terms of making sure the interface is
something we'll be happy with, that ties in nicely with the exiting Forms
API style, and with dealing with both serialization and de-serialization,
but I think what we have now looks about right. (Positive criticisms are
very welcomed of course.)
Prob. best to take any further discussion to the dev list.
--
Ticket URL: <https://code.djangoproject.com/ticket/4656#comment:29>
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.
