Opened 15 years ago
Last modified 15 years ago
#13145 new New feature
Allow the prefix used for empty_form on FormSets to be customized
Reported by: | Alex Gaynor | Owned by: | nobody |
---|---|---|---|
Component: | Forms | Version: | dev |
Severity: | Normal | Keywords: | |
Cc: | Triage Stage: | Accepted | |
Has patch: | yes | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | yes |
Easy pickings: | no | UI/UX: | no |
Pull Requests: | How to create a pull request | ||
Description ¶
According to the ticket's flags, the next step(s) to move this issue forward are:
- To improve the patch as described in the pull request review comments or on this ticket, then uncheck "Patch needs improvement".
If creating a new pull request, include a link to the pull request in the ticket comment when making that update. The usual format is:
[https://github.com/django/django/pull/#### PR]
.
Change History (8)
by , 15 years ago
Attachment: | custom-empty-form-prefix.diff added |
---|
by , 15 years ago
Attachment: | custom-empty-form-prefix.2.diff added |
---|
comment:1 by , 15 years ago
Patch needs improvement: | set |
---|---|
Triage Stage: | Unreviewed → Accepted |
by , 15 years ago
Attachment: | custom-empty-form-prefix.3.diff added |
---|
comment:2 by , 14 years ago
Type: | → New feature |
---|
comment:3 by , 14 years ago
Severity: | → Normal |
---|
Note:
See TracTickets
for help on using tickets.
To clarify - the use case here is for nested inlines; if you add a new row that itself contains pre-existing inline rows, the prefix subsitution occurs on both the base and the nested form.
The test case needs to be elaborated to make sure we protect against this use case.