#28176: Expose real (i.e. not converted to string) value in widget option
context
--------------------------------+------------------------------------
Reporter: Moritz Sichert | Owner: nobody
Type: New feature | Status: new
Component: Forms | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------+------------------------------------
Changes (by Tim Graham):
* has_patch: 0 => 1
Comment:
On the PR for #28303
[https://github.com/django/django/pull/8639#issuecomment-308612817 John
suggested], "If this lands, the option's input's value could be added to
the attrs dict in `Widget.create_option()`, then value could resume to be
the actual value, not the coerced value." I implemented that idea in the
second commit of a [https://github.com/django/django/pull/8646 PR], then
simplified things to what I think is a simpler approach in the third
commit.
--
Ticket URL: <https://code.djangoproject.com/ticket/28176#comment:4>
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/065.389670395b3f1e1fc9202860065fc330%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
