#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
-------------------------------+------------------------------------
Changes (by timgraham):
* needs_better_patch: => 0
* version: 1.7 => master
* needs_tests: => 0
* needs_docs: => 0
* stage: Unreviewed => Accepted
Comment:
Just because something is "widely used" isn't a justification for making
it a public API, but we recently documented `Form.has_changed()` so it
probably makes sense to document this as well. This method relies on
`field.show_hidden_initial` which also isn't documented so we might want
to consider that as well.
We should likely address the comment in the `changed_data` property `XXX:
For now we're asking the individual fields ...` before documenting this
though as if we make that change it might be easier to do so before
documenting in case there are any backwards compatibility concerns.
--
Ticket URL: <https://code.djangoproject.com/ticket/24191#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 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.05404c3629e464a081fb6af0d9e1df17%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
