Opened 8 years ago

Closed 8 years ago

#6690 closed (wontfix)

Document the dynamic use of ModelForms classes

Reported by: jdetaeye Owned by: nobody
Component: Documentation Version: master
Severity: Keywords: modelforms
Cc: Triage Stage: Unreviewed
Has patch: yes Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: UI/UX:

Description

Dynamically creating model forms is a fairly common use case, especially for users of the deprecated form_for_model and form_for_instance methods.
The modelforms class easily allows this, but the correct way to achieve it is not very obvious (except to more advanced Python programmers).
Documenting the right way should overcome this...

Attachments (1)

modelforms.patch (721 bytes) - added by jdetaeye 8 years ago.
modelforms documentation update

Download all attachments as: .zip

Change History (2)

Changed 8 years ago by jdetaeye

modelforms documentation update

comment:1 Changed 8 years ago by brosner

  • Needs documentation unset
  • Needs tests unset
  • Patch needs improvement unset
  • Resolution set to wontfix
  • Status changed from new to closed

I disagree this is a common case. The reason the ModelForm class was created was to avoid this entirely and to leave people who still needed this functionality to either learn it or just use it outside the framework. I am closing this ticket because this shouldn't be described in the docs and would be better in the wiki since it is a special case. Plus this is simply Python. People can use django-users to get at learning how or just searching Google.

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