Opened 15 years ago
Closed 15 years ago
#16125 closed Cleanup/optimization (duplicate)
document BoundField's id_for_label attribute
| Reported by: | Owned by: | nobody | |
|---|---|---|---|
| Component: | Documentation | Version: | 1.3 |
| Severity: | Normal | Keywords: | boundfield forms |
| Cc: | Triage Stage: | Design decision needed | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | yes | UI/UX: | no |
Description
As there is no separate documentation on BoundField -- its just rolled into the page on forms -- it would be good to have additional fields even passingly documented under the section on looping over the form's fields. Specifically, it may be necessary on occassion to target one field with more than one label, which requires knowledge of BoundField.id_for_label or rooting through the source code.
I'd be tempted to also document css_classes and auto_id, although I suppose auto_id could be considered private?https://code.djangoproject.com/browser/django/trunk/django/forms/forms.py
Change History (1)
comment:1 by , 15 years ago
| Resolution: | → duplicate |
|---|---|
| Status: | new → closed |
| Triage Stage: | Unreviewed → Design decision needed |
Note:
See TracTickets
for help on using tickets.
This is a duplicate of #12856.