#27679 closed Cleanup/optimization (fixed)
Document that empty formsets display min_num+extra forms
| Reported by: | Lorenzo Peña | Owned by: | David Smith |
|---|---|---|---|
| Component: | Documentation | Version: | 1.9 |
| Severity: | Normal | Keywords: | |
| Cc: | Triage Stage: | Accepted | |
| Has patch: | yes | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
I already read #22628
To me: min_num is an option for validation and extra is an option for presentation
Currently, in an empty formset, you get min_num+extra empty forms, I think it should be max(min_num, extra) instead
Change History (5)
comment:1 by , 9 years ago
| Component: | Uncategorized → Forms |
|---|---|
| Summary: | Formsets: min_num and extra → Empty formsets should display max(min_num, extra) rather than min_num+extra |
| Type: | Uncategorized → Cleanup/optimization |
comment:2 by , 9 years ago
| Component: | Forms → Documentation |
|---|---|
| Summary: | Empty formsets should display max(min_num, extra) rather than min_num+extra → Document that empty formsets display min_num+extra forms |
| Triage Stage: | Unreviewed → Accepted |
Looks like this was considered previously and rejected due to backwards compatibility. Tentatively accepting as a documentation enhancement pending no further arguments to change the behavior.
comment:3 by , 5 years ago
| Has patch: | set |
|---|---|
| Owner: | changed from to |
| Status: | new → assigned |
Note:
See TracTickets
for help on using tickets.
You should say a little more to strengthen your proposal. For example, what are the ramifications for backwards compatibility? What does the documentation say about this?