#24191: form.changed_data appears to be undocumented
-------------------------------+------------------------------------
Reporter: rhertzog | Owner: nobody
Type: New feature | Status: new
Component: Documentation | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+------------------------------------
Comment (by alasdairnicol):
I have created a pull request https://github.com/django/django/pull/4768
which documents form.changed_data.
I haven't addressed the comment that tim refers to. Changing the
implementation of ``has_changed`` to use a hidden field would have
backwards incompatibility implications for `form.has_changed()` (which is
documented) as well.
I may have misunderstood the suggestion in the comments, but am not sure
that the the hidden field approach is better. Not every form is
instantiated from a `request.POST` or request.GET that contains a hidden
field.
--
Ticket URL: <https://code.djangoproject.com/ticket/24191#comment:2>
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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/066.51690d6dfaaeec322e3ab73ed114f7ba%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
