#16905 closed New feature (fixed)
Custom fields and apps should have a way to hook into BaseCommand.validate
| Reported by: | Jeremy Dunck | Owned by: | nobody |
|---|---|---|---|
| Component: | Core (Management commands) | Version: | dev |
| Severity: | Normal | Keywords: | |
| Cc: | Triage Stage: | Accepted | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
Right now, management.validation.get_validation_errors has a long chain of elif isinstance's for built-in fields.
It should be possible for custom fields to participate in this model-declaration validation phase.
Change History (7)
comment:1 Changed 12 years ago by
| Triage Stage: | Unreviewed → Accepted |
|---|---|
| Version: | 1.3 → SVN |
comment:2 Changed 12 years ago by
| Summary: | Custom fields should be included in BaseCommand.validate → Custom fields and apps should have a way to hook into BaseCommand.validate |
|---|
Not only custom fields, but also things that aren't fields at all - e.g. #8579.
comment:3 Changed 9 years ago by
A pull request to address this issue is now available, and is a candidate for the 1.7 release.
comment:4 Changed 9 years ago by
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Note: See
TracTickets for help on using
tickets.
Definitely. Both #3055 and #8579 are waiting on this.