#6735: Class-based generic views
------------------------------------+---------------------------------------
Reporter: jkocherhans | Owner: telenieko
Status: assigned | Milestone: post-1.0
Component: Generic views | Version: SVN
Resolution: | Keywords:
Stage: Accepted | Has_patch: 1
Needs_docs: 1 | Needs_tests: 0
Needs_better_patch: 0 |
------------------------------------+---------------------------------------
Comment (by jkocherhans):
Replying to [comment:18 telenieko]:
> Question of the day, mostly for jacob and jkocherhans (it's DDN):
>
> * Would you agree to add to DetailView and ListView (see
[http://www.marcfargas.com/gitweb/?p=django.git;a=commitdiff;h=trac/6735
-class-based-generic-views;hp=master current diff]) an extra option:
"allow_serialization" (and maybe "serialization_format='json'") and then,
in the __call__() do:
This seems more in the realm of the various REST projects going on, so I'd
be -0. People are going to want to control which fields are serialized,
and that is definitely out of scope for {{{DetailView}}} and
{{{ListView}}}.
--
Ticket URL: <http://code.djangoproject.com/ticket/6735#comment:19>
Django Code <http://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 [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---