-
|
After looking for it in documentation, all examples uses some kind of FormView. I'm looking to migrate an already existing project with hundreds of function based views... |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
|
As always, it depends. If your are using a widget which requires an endpoint, such as the Selectize- or FileUpload-widget, then this extra endpoint must be handled somewhere. Therefore django-formset makes heavy use of special view mixin classes, such as IncompleteSelectResponseMixin, FileUploadMixin. For widgets which do not require an endpoint, some requests and responses must be altered. Here it might be possible to proceed with function based views. However, I believe it is less work to migrate them to classed based views rather than altering the request and response in those functions. |
Beta Was this translation helpful? Give feedback.
As always, it depends.
If your are using a widget which requires an endpoint, such as the Selectize- or FileUpload-widget, then this extra endpoint must be handled somewhere. Therefore django-formset makes heavy use of special view mixin classes, such as IncompleteSelectResponseMixin, FileUploadMixin.
For widgets which do not require an endpoint, some requests and responses must be altered. Here it might be possible to proceed with function based views. However, I believe it is less work to migrate them to classed based views rather than altering the request and response in those functions.