IProjectSet.search() has unused untested optional arguments
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Fix Released
|
Low
|
j.c.sackett |
Bug Description
Both IProductSet.
These arguments can be used via the productset and projectset views by URL hacking. For example:
https:/
However there is nothing in the page templates that would let a user do this (I think they used to be visible a long time ago). One of the following should be done:
* expose the checkboxes in the page templates, and add tests
* remove support for these constraints from the view classes and database classes
* remove support for these constraints from the view classes, but leave them in the DB classes and add tests.
Related branches
- Graham Binns (community): Approve (code)
-
Diff: 86 lines (+3/-35)3 files modifiedlib/lp/registry/browser/project.py (+1/-13)
lib/lp/registry/interfaces/projectgroup.py (+1/-4)
lib/lp/registry/model/projectgroup.py (+1/-18)
Changed in launchpad: | |
importance: | Untriaged → Low |
status: | Unconfirmed → Confirmed |
Changed in launchpad-registry: | |
status: | Confirmed → Triaged |
Changed in launchpad-registry: | |
milestone: | 2.2.8 → none |
assignee: | Barry Warsaw (barry) → nobody |
tags: |
added: tech-debt removed: infrastructure |
Changed in launchpad-registry: | |
milestone: | 3.1.10 → none |
tags: | removed: post-3-ui-cleanup |
Changed in launchpad-registry: | |
status: | Triaged → In Progress |
assignee: | nobody → j.c.sackett (jcsackett) |
tags: |
added: qa-ok removed: qa-needstesting |
Changed in launchpad-registry: | |
status: | Fix Committed → Fix Released |
For IProductSet, those arguments are also completely untested.
The entire test suite calls the method only in one place (bugtask- adding- pages.txt, from bugalsoaffects.py) and only the first parameter is used. Breaking that method only breaks that test, and all tests pass if the method is made to break whenever any of the other arguments is given.
Also, the rosetta argument produces invalid SQL: see bug 1415.