#16306: Form field documentation documents optional keyword arguments as field
attributes.
-------------------------------------+-------------------------------------
Reporter: ShawnMilo | Owner: nobody
Type: Bug | Status: reopened
Milestone: | Component: Forms
Version: SVN | Severity: Normal
Resolution: | Keywords: form field
Triage Stage: Design | documentation
decision needed | Has patch: 0
Needs documentation: 1 | Needs tests: 1
Patch needs improvement: 0 | Easy pickings: 1
UI/UX: 0 |
-------------------------------------+-------------------------------------
Changes (by ShawnMilo):
* component: Documentation => Forms
* stage: Accepted => Design decision needed
Comment:
Also, a comment about using one of the following workarounds:
1. Replace the field completely in the form's __init__.
2. Add the field in the form's __init__ (don't have it in the original
definition).
Both of these would cause confusion for the maintenance developer: Either
a field is appearing 'by magic' or it's not as defined in the form
originally. Neither case is desirable.
--
Ticket URL: <https://code.djangoproject.com/ticket/16306#comment:3>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
