#17210: Make NullBooleanSelect for NullBooleanField pass true/false as a GET
parameter
-------------------------------------------------+--------------------
Reporter: anatoly techtonik <techtonik@…> | Owner: nobody
Type: Bug | Status: new
Component: Forms | Version: 1.2
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 1
-------------------------------------------------+--------------------
Currently, NullBooleanSelect uses form with the following parameters:
{{{
choices = ((u'1', ugettext('Unknown')), (u'2', ugettext('Yes')), (u'3',
ugettext('No')))
}}}
which generates URLs like `?param=3` for `Param: No` selection and
`?param=1` for `Param: Unknown`. This makes URLs pretty counter-intuitive
for search forms. For example, imaging search for issues. If you need to
find all closed issues, the URL will be `?closed=3`, not `?closed=1` as
you may assume for boolean field.
It will be more user-friendly to generate `param=`, `param=true` and
`param=false` for boolean field URLs.
--
Ticket URL: <https://code.djangoproject.com/ticket/17210>
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 post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
