Opened 5 years ago

Last modified 5 years ago

#17210 new Cleanup/optimization

Make NullBooleanSelect for NullBooleanField pass true/false as a GET parameter

Reported by: anatoly techtonik <techtonik@…> Owned by: nobody
Component: Forms Version: master
Severity: Normal Keywords:
Cc: Triage Stage: Accepted
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: yes


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.

Change History (1)

comment:1 Changed 5 years ago by Aymeric Augustin

Needs documentation: unset
Needs tests: unset
Patch needs improvement: unset
Triage Stage: UnreviewedAccepted
Type: BugCleanup/optimization
Version: 1.2SVN

I'm accepting the idea on principle, but I'd like to see a thorough analysis of how much backwards-incompatibility this change introduces.

Note: See TracTickets for help on using tickets.
Back to Top