Opened 23 months ago
Closed 23 months ago
#34307 closed Bug (needsinfo)
Issue with min_num logic in InlineFormsets
| Reported by: | Suyash Singh | Owned by: | nobody |
|---|---|---|---|
| Component: | Forms | Version: | 4.1 |
| Severity: | Normal | Keywords: | forms |
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
So, seeing the Django code there are two fields min_num and extra keyword. There is a straightforward coorelation between the two that is, if min_num is provided then extra should atleast be equal or greater than min_num.
This is causing ordering issue in Wagtail Admin Form page, where initial extra forms are not created because extra is None but min_num arguement is passed, this leads to ordering issue in the inline formsets.
I would like to work on this issue but would like some guidance, thank you!
Change History (2)
comment:1 by , 23 months ago
comment:2 by , 23 months ago
| Resolution: | → needsinfo |
|---|---|
| Status: | new → closed |
Please reopen the ticket if you can provide a sample project (without Wagtail) which reproduces the issue.
The ordering field is only pre-filled for initial forms from a19ed8aea395e8e07164ff7d85bd7dff2f24edca (2008).
I didn't read the linked issue, but from what's here, I'm not sure you've described the problem sufficiently. Can you flesh it out with some example code that doesn't involve Wagtail?