#16174: Class based view update for FormPreview
--------------------------------------+------------------------------------
Reporter: ryankask | Owner: ryankask
Type: Cleanup/optimization | Status: new
Component: contrib.formtools | Version: 1.3
Severity: Normal | Resolution:
Keywords: formpreview, preview | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 1
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
--------------------------------------+------------------------------------
Comment (by ryankask):
That approach is definitely best.
I think some sort of mixin as AndrewIngram mentioned would be ideal.
My initial thoughts are thoughts are that a mixin would be a bit brittle
because its `post` method would always need to be resolved first with
respect to the inheritance tree.
Another option would be to replace the `ProcessFormView` and provide new
bases for the create, update, and delete views in the new form preview
package.
Or maybe I'm just not thinking outside the box ;) I will have a look this
weekend and report back.
--
Ticket URL: <https://code.djangoproject.com/ticket/16174#comment:9>
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.
