#21654: Document a use-case for `Form.errors.as_data()`
--------------------------------------+------------------------------------
Reporter: selwin | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: Forms | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
--------------------------------------+------------------------------------
Changes (by bmispelon):
* stage: Unreviewed => Accepted
* easy: 0 => 1
Comment:
I agree with Tim that a documentation update would help clear up the
confusion.
Why would a user want to use `form.errors.as_data()` instead of just
`form.errors`; is there a use-case for it?
I'm accepting the ticket on this basis.
--
Ticket URL: <https://code.djangoproject.com/ticket/21654#comment:9>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/064.886831c7e71c3a89ba7b5ca80c16e392%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.
