Closed Bug 914318 Opened 11 years ago Closed 11 years ago

In Collections API, return filters used in a response header when fallback mechanism is used

Categories

(Marketplace Graveyard :: API, defect, P2)

Product:
Marketplace Graveyard
Component:
API
Platform:
x86_64
Linux
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED FIXED
Milestone:
2013-09-24

People

(Reporter: mat, Assigned: mat)

References

Details

(Whiteboard: [qa-])

In the Collections API, when specifying some filters, if there are no results a fallback mechanism kicks in to try to find results with a different combination of filters, sometimes even dropping some in the process. We need a) some documentation b) a way for a client to know its query has been filtered, possibly in the response headers. We already have a API-Filter header, maybe re-use that. (See "FIXME: add current filter set to API-Filter in response")
Assignee: nobody → mpillard
Priority: -- → P3
The fallback system will no longer completely drop filters when bug 915803 is done. I tried implementing this but it's actually pretty difficult, it would require changing too much code to be worth it, IMHO. Since the fallback will be less complex with bug 915803, I'm un-assigning myself and lowering priority.
Assignee: mpillard → nobody
Priority: P3 → P4
Turns out I had forgotten the other part of this bug which is documentation. I'll try to come up with something.
Priority: P4 → P3
Assignee: nobody → mpillard
Status: NEW → ASSIGNED
Priority: P3 → P2
Target Milestone: --- → 2013-09-24
Fixed in https://github.com/mozilla/zamboni/commit/17a7eac23d5a6aa132fa19c52b9efb2081daabf7 Rocketfuel API now exposes API-Fallback in listing URLs, when fallback was used. Documentation was updated.
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Whiteboard: [qa-]
You need to log in before you can comment on or make changes to this bug.