Code

Opened 6 years ago

Closed 6 years ago

Last modified 5 years ago

#8860 closed (invalid)

Where should form classes and formset classes be defined?

Reported by: r.topor@… Owned by: nobody
Component: Documentation Version: master
Severity: Keywords: forms
Cc: Triage Stage: Unreviewed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: UI/UX:

Description

The current documentation doesn't say where form classes and formset classes and so on should be defined. Should they be defined in module models.py or in a separate module forms.py or somewhere else altogether? I think the situation is analogous to admin information which eventually was moved from models.py to admin.py.

Attachments (0)

Change History (3)

comment:1 Changed 6 years ago by Rodney Topor <r.topor@…>

  • Needs documentation unset
  • Needs tests unset
  • Patch needs improvement unset
  • Version changed from 1.0 to SVN

comment:2 Changed 6 years ago by ubernostrum

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

There's no requirement that they be defined in any specific place; you're free to define your form-related stuff anywhere you like. For further questions, please consult the archives of the django-users list, where questions about best practices for application layout have been discussed multiple times.

comment:3 Changed 5 years ago by anonymous

  • milestone post-1.0 deleted

Milestone post-1.0 deleted

Add Comment

Modify Ticket

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


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

 
Note: See TracTickets for help on using tickets.