Opened 8 years ago
Last modified 2 years ago
#27923 new New feature
Add form signals (pre_init, post_init, pre_clean, post_clean, etc.)
| Reported by: | David Seddon | Owned by: | |
|---|---|---|---|
| Component: | Forms | Version: | |
| Severity: | Normal | Keywords: | forms, signals |
| Cc: | Triage Stage: | Accepted | |
| Has patch: | yes | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | yes |
| Easy pickings: | no | UI/UX: | no |
Description
Adding some signals for forms would allow apps to plug in to other apps and aid encapsulation between apps.
More discussion here: https://groups.google.com/forum/?utm_medium=email&utm_source=footer#!msg/django-developers/SviNiWy3Bjc/fqFL8rZvBAAJ
Proposed signals:
- pre_init
- post_init
- pre_clean
- post_clean
And for ModelForm:
- pre_save
- post_save
I'd be happy to do a pull request for this one.
Change History (5)
comment:1 by , 8 years ago
| Summary: | Forms signals → Add form signals (pre_init, post_init, pre_clean, post_clean, etc.) |
|---|---|
| Triage Stage: | Unreviewed → Accepted |
comment:2 by , 8 years ago
| Owner: | changed from to |
|---|---|
| Status: | new → assigned |
comment:4 by , 8 years ago
| Patch needs improvement: | set |
|---|
comment:5 by , 2 years ago
| Owner: | removed |
|---|---|
| Status: | assigned → new |
Note:
See TracTickets
for help on using tickets.
Nominally accepted, though as discussed on the mailing list, details remain to be determined.