#24010: Unable to use choice values instead of choice keys in form/field
validation
-------------------------------------+-------------------------------------
Reporter: karolyi | Owner: nobody
Type: New feature | Status: closed
Component: Forms | Version: 1.7
Severity: Normal | Resolution: needsinfo
Keywords: field choices error | Triage Stage:
display | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by karolyi):
Exactly. This way, the choice names would not have been exposed for the
user, because they might not make sense for him. However, exposing the
choice value, which is often used as a label, would be valuable.
Replying to [comment:2 timgraham]:
> I'm not sure I understand -- could you give an example?
>
> If you have a field like:
> `models.CharField(max_length=1, choices=(('A', 'ABC'), ('X', 'XYZ')))`
> but the POST data contains 'B', you want a different error message from
"Select a valid choice. B is not one of the available choices."?
--
Ticket URL: <https://code.djangoproject.com/ticket/24010#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.27c3b2ec264edfd7f384f6db8ac40aaa%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
