Closed Bug 907990 Opened 11 years ago Closed 11 years ago

`remove_app` collection endpoint should not throw 400 if app is not in collection

Categories

(Marketplace Graveyard :: API, defect)

Product:
Marketplace Graveyard
Component:
API
Platform:
x86
macOS
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
VERIFIED FIXED
Milestone:
2013-08-27

People

(Reporter: basta, Assigned: chuck)

References

Details

(Whiteboard: p=1 [qa-]) 

Idempotence! If the app is not in the collection, then that's what the API client wants. Perhaps the server should return a 205 to indicate that the client should probably refresh.
I'll buy a 205.
Status: NEW → ASSIGNED
Whiteboard: p=1
Target Milestone: --- → 2013-08-27
Assignee: nobody → charmston
Landed: https://github.com/mozilla/zamboni/compare/ef1f1849f420...0947f220453a
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Whiteboard: p=1 → p=1 [qa-]
FWIW, this bug (and others like it) does not need to be [qa-]. This ought to be pretty easy to verify.
Fair enough. My logic was that it's something easy enough for basta to verify, rather than spending QA resources on it.
Verified.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.