Opened 9 years ago

Closed 9 years ago

Last modified 9 years ago

#2819 closed enhancement (wontfix)

Generic views for manipulators

Reported by: r.pelizzi@… Owned by: adrian
Component: contrib.admin Version:
Severity: normal Keywords: generic view, manipulator
Cc: Triage Stage: Unreviewed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: UI/UX:

Description

As far as i know, there are very handy generic views for creating, updating objects. Their limit is that you have to use them on an object, and they use the object's default manipulator. What if my manipulator doesn't have a related object (e.g. i have a manipulator that creates two objects)? And what if want to use a different manipulator? Since the view code to use the manipulator is essentially the same, this calls for a generic view. Then django can be enhanched in 2 ways:

  1. Provide a way to assign manipulators to objects to replace the auto-generated one (altough this would mess up the admin i think)
  1. Provide a generic view which accepts a manipulator rather than an object. We're not even using the original object in the context of the create_object generic view! I could provide one myself, although you could probably write it in 3 seconds and be more consistent with the arguments required.

Change History (1)

comment:1 Changed 9 years ago by ubernostrum

  • Resolution set to wontfix
  • Status changed from new to closed

I'm marking this wontfix because it's come up before and been closed before; the manipulator system is being pulled out and will be replaced with a different framework (see discussions on the django-developers list for details) in the not-too-distant future, so building in additional support for the current system doesn't make a lot of sense.

Once the new system is in place, if this is still an issue, please file a new ticket.

Note: See TracTickets for help on using tickets.
Back to Top