#30689: Fix documentation for the `fields` argument of MultiValueField
-------------------------------+--------------------------------------
Reporter: Adam Sołtysik | Owner: nobody
Type: Bug | Status: closed
Component: Documentation | Version: master
Severity: Normal | Resolution: invalid
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------------------------
Changes (by Carlton Gibson):
* status: new => closed
* type: Uncategorized => Bug
* version: 2.2 => master
* resolution: => invalid
Comment:
Without actual code it's difficult to know what's broken in your project
but I'd guess the relevant change was #28192. Optional args are now
keyword only. As [https://docs.djangoproject.com/en/2.2/releases/2.0
/#form-fields-no-longer-accept-optional-arguments-as-positional-arguments
per the note in the Backwards incompatible changes section of the 2.0
release notes]:
> To help prevent runtime errors due to incorrect ordering of form field
arguments, optional arguments of built-in form fields are no longer
accepted as positional arguments.
In general, the reference docs do not attempt to match the code signature
of the documented methods exactly. Rather they aim to give a guide to the
interface from the user perspective. In this case, `fields` doesn't have
an actual default, but is a required tuple of fields, as per the
discussion below.
--
Ticket URL: <https://code.djangoproject.com/ticket/30689#comment:1>
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 unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/065.daa3fafc9d0e599c58636ff41d611609%40djangoproject.com.
