#21792: Form.has_changed is not documented
-------------------------------------+-------------------------------------
Reporter: bjb@… | Owner: navi7
Type: Bug | Status: assigned
Component: Documentation | Version: 1.6
Severity: Normal | Resolution:
Keywords: has_changed api | Triage Stage: Accepted
ModelForm | Needs documentation: 0
Has patch: 1 | Patch needs improvement: 1
Needs tests: 0 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Comment (by timo):
I don't see a reason it shouldn't be. It got a mention in the 1.6 release
notes: "If you defined your own form widgets and defined the
`_has_changed()` method on a widget, you should now define this method on
the form field itself." and seems useful for custom fields (e.g.
`ReadOnlyPasswordHashField` in `contrib.auth` uses it. I'm not sure it's
worth the code church to rename it to `has_changed()` (removing the
underscore) before making it official. #16612 was the ticket where it
moved from widgets to fields and would have been a good time to make the
change if we were going to do it.
--
Ticket URL: <https://code.djangoproject.com/ticket/21792#comment:8>
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/072.98b0d82a461fd128350479b7def720f0%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
