Bug searches should be case-insensitive with respect to status values
Bug #154556 reported by
Brad Crittenden
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Fix Released
|
Critical
|
Tim Penhey | ||
lazr.enum |
Fix Released
|
Critical
|
Tim Penhey |
Bug Description
Searches should not be case-sensitive with respect to the values passed as importance, status, etc.
The following search generates an OOPS because we use 'critical' instead of 'Critical':
https:/
For the feeds project we'd like to normalize the query string for caching performance. To do that we sort the query string and would like to use a normalized case by converting the entire query string to lower case. Currently that is not possible.
Related branches
lp:~thumper/lazr.enum/case-insensitive-getTokenByTerm
- Gavin Panella: Approve
-
Diff: 47 lines (+16/-2)3 files modifiedHACKING.txt (+10/-0)
src/lazr/enum/README.txt (+3/-0)
src/lazr/enum/_enum.py (+3/-2)
lp:~thumper/launchpad/bug-search-insensitive
- Tim Penhey (community): Approve
-
Diff: 12 lines (+1/-1)1 file modifiedversions.cfg (+1/-1)
Changed in launchpad-registry: | |
importance: | Medium → Low |
status: | Confirmed → Triaged |
Changed in launchpad: | |
importance: | High → Critical |
Changed in lazr.enum: | |
status: | New → In Progress |
assignee: | nobody → Tim Penhey (thumper) |
importance: | Undecided → Medium |
Changed in lazr.enum: | |
importance: | Medium → Critical |
Changed in lazr.enum: | |
status: | In Progress → Fix Released |
milestone: | none → 1.1.3 |
Changed in launchpad: | |
status: | Triaged → In Progress |
assignee: | nobody → Tim Penhey (thumper) |
tags: | added: qa0ok |
tags: |
added: qa-ok removed: qa0ok |
Changed in launchpad: | |
status: | In Progress → Fix Released |
To post a comment you must log in.
lazr.enum handles title and token, but not cases-insensiti vity. So while it is backwards compatible, it is not forward looking. I think Item and DBItem need revision to make our URLs lowercase.