Opened 2 years ago

Closed 23 months ago

#17700 closed Cleanup/optimization (invalid)

Django formset documentation missing Class Based View Docs

Reported by: rh0dium Owned by: Fandekasp
Component: Documentation Version: 1.3
Severity: Normal Keywords:
Cc: lemaire.adrien@… Triage Stage: Accepted
Has patch: yes Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no


Hi all,

I understand that CBV's are supported and that there is push to use them moving forward. Please update the documentation on how to properly use formsets in class based views (Create/Edit/Update). Currently there is little documentation on this. I have seen ticket 16256 but those aren't supported as of yet. CBV's are supported and the docs needs to reflect that.

Attachments (1)

cbv_formsets_doc.diff (1.4 KB) - added by Fandekasp 2 years ago.
Add an example for using Formsets with class based views

Download all attachments as: .zip

Change History (7)

comment:1 Changed 2 years ago by anonymous

  • Needs documentation unset
  • Needs tests unset
  • Patch needs improvement unset

comment:2 Changed 2 years ago by aaugustin

  • Component changed from Uncategorized to Documentation
  • Type changed from Uncategorized to Cleanup/optimization

comment:3 Changed 2 years ago by aaugustin

  • Triage Stage changed from Unreviewed to Accepted

comment:4 Changed 2 years ago by Fandekasp

  • Owner changed from nobody to Fandekasp

Changed 2 years ago by Fandekasp

Add an example for using Formsets with class based views

comment:5 Changed 2 years ago by Fandekasp

  • Cc lemaire.adrien@… added
  • Has patch set

Please review and test my example.

comment:6 Changed 23 months ago by rasca

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

Hi, I'm going to close this as we are preparing class based generic views for formsets and there's were we will be adding the documentation. Adding docs about creating a formset cbv sounds more like a tutorial on how to make your own generic cbv (which is not a bad thing, but that sound like a separate ticket).

If you'd like to chime in in ticket #16256 you are more than welcome! I'm not an english native speaker and docs is always my weakest front. Any help we'll be much appreciated.

Add Comment

Modify Ticket

Change Properties
<Author field>
as closed
as The resolution will be set. Next status will be 'closed'
The resolution will be deleted. Next status will be 'new'

E-mail address and user name can be saved in the Preferences.

Note: See TracTickets for help on using tickets.