#4656: Allow In-depth serialization by specifying depth to follow relationship
--------------------------------------+------------------------------------
Reporter: jay.m.martin@… | Owner: nobody
Type: New feature | Status: closed
Component: Core (Serialization) | Version:
Severity: Normal | Resolution: wontfix
Keywords: feature | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
--------------------------------------+------------------------------------
Changes (by tomchristie):
* status: new => closed
* resolution: => wontfix
Comment:
Unless theres a more fundamental addressing of the serialization API,
aimed at making it *generally* usable and extendable for Web APIs I don't
see any value in pushing the scope of the serializers as they now stand.
Right now the use case for them should be for fixture loading and saving
and nothing else. There are better tools out there for generally
extendable serialization schemes (REST framework, tastypie, etc).
Could we address tickets like this? Sure, but not until and unless we're
doing that in the context of a fully fledged serializer API that's
properly suitable for meeting the use cases of both Web APIs *and* fixture
generation.
--
Ticket URL: <https://code.djangoproject.com/ticket/4656#comment:31>
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/080.a605b96a2eb16fb38505703ff6389ab9%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
