Opened 15 years ago
Closed 13 years ago
#13465 closed Cleanup/optimization (duplicate)
non_field_errors should be mentioned in the form api docs
| Reported by: | Chris Beaven | Owned by: | nobody |
|---|---|---|---|
| Component: | Documentation | Version: | dev |
| Severity: | Normal | Keywords: | |
| Cc: | Triage Stage: | Accepted | |
| Has patch: | no | Needs documentation: | yes |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
Change History (7)
comment:1 by , 15 years ago
| Resolution: | → worksforme |
|---|---|
| Status: | new → closed |
| Triage Stage: | Unreviewed → Accepted |
comment:2 by , 15 years ago
| Resolution: | worksforme |
|---|---|
| Status: | closed → reopened |
| Triage Stage: | Accepted → Design decision needed |
Sorry, I should have been more specific: I was thinking perhaps a crossreferencing sentence at the end of http://docs.djangoproject.com/en/1.1/ref/forms/api/#more-granular-output
This came from an IRC discussion and I had to hunt for the reference to non_field_errors.
I'll reopen for a decision to be made on whether that'd just be noise or a useful reference
comment:3 by , 15 years ago
| Needs documentation: | set |
|---|---|
| Triage Stage: | Design decision needed → Accepted |
This came up again in IRC.
Reviewing the current docs again, the usage methods are inferred here, but never explicitly shown how they could be used (common usage as opposed to the current mention in custom validation docs).
comment:4 by , 15 years ago
| Severity: | → Normal |
|---|---|
| Type: | → Cleanup/optimization |
comment:7 by , 13 years ago
| Resolution: | → duplicate |
|---|---|
| Status: | reopened → closed |
This looks like a duplicate of #14023 which was closed in 0f9eb912ffa015574ebb2d1fd6a2a78664a19039.
Note:
See TracTickets
for help on using tickets.
non_field_errors is mentioned in the form docs. If you think there is a need for something else, you'll need to be a little more specific.