#36212: How about providing type safe access to form field data?
------------------------------+--------------------------------------
Reporter: Justin Black | Owner: (none)
Type: New feature | Status: closed
Component: Forms | Version: 5.1
Severity: Normal | Resolution: wontfix
Keywords: form, field | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
------------------------------+--------------------------------------
Changes (by Sarah Boyce):
* component: Uncategorized => Forms
* resolution: => wontfix
* status: new => closed
* type: Uncategorized => New feature
Comment:
As this is requesting a new feature for Django. The recommended path
forward is to first propose and discuss the idea with the community and
gain consensus. To do that, please consider starting a new conversation on
the [https://forum.djangoproject.com/c/internals/5 Django Forum], where
you'll reach a broader audience and receive additional feedback.
I'll close the ticket for now, but if the community agrees with the
proposal, please return to this ticket and reference the forum discussion
so we can re-open it. For more information, please refer to
[https://docs.djangoproject.com/en/stable/internals/contributing/bugs-and-
features/#requesting-features the documented guidelines for requesting
features].
I also recommend you look for similar type conversations and try to
incorporate or summarize opinions from these.
--
Ticket URL: <https://code.djangoproject.com/ticket/36212#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 view this discussion visit
https://groups.google.com/d/msgid/django-updates/01070195371ae9b5-7e724fd9-36ee-4c74-b04a-a25998830307-000000%40eu-central-1.amazonses.com.
