At the moment, writing custom admin
actions<https://docs.djangoproject.com/en/dev/ref/contrib/admin/actions/#actions-as-modeladmin-methods>requires
an old style view function that returns a Response object. The
signature for this is similar to a old function-based view (except with
modeladmin before request):
func(modeladmin, request, queryset):
...
return HttpResponse()
I wanted to write an action with an intermediate
page<https://docs.djangoproject.com/en/dev/ref/contrib/admin/actions/#actions-that-provide-intermediate-pages>,
but using class based views (for uniformity across my app). This doesn't
seem to be doable without writing a custom base View object
<https://github.com/django/django/blob/master/django/views/generic/base.py#L27>that
interprets the
view args in a different order. By switching the function signature for
actions and putting the request first, wouldn't this it very easy to plugin
class based views when writing actions.
Does this make sense and is it worth a feature request (or a bit more
research)?
Timmy
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at http://groups.google.com/group/django-developers?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
