If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

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

VERIFIED FIXED in 2013-08-27

Status

Marketplace
API
VERIFIED FIXED
4 years ago
4 years ago

People

(Reporter: basta, Assigned: chuck)

Tracking

2013-08-27
x86
Mac OS X
Points:
---

Details

(Whiteboard: p=1 [qa-])

(Reporter)

Description

4 years ago
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.
Blocks: 894417
(Assignee)

Comment 1

4 years ago
I'll buy a 205.
Status: NEW → ASSIGNED
Whiteboard: p=1
Target Milestone: --- → 2013-08-27
(Assignee)

Updated

4 years ago
Assignee: nobody → charmston
(Assignee)

Comment 2

4 years ago
Landed: https://github.com/mozilla/zamboni/compare/ef1f1849f420...0947f220453a
Status: ASSIGNED → RESOLVED
Last Resolved: 4 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.
(Assignee)

Comment 4

4 years ago
Fair enough. My logic was that it's something easy enough for basta to verify, rather than spending QA resources on it.
(Reporter)

Comment 5

4 years ago
Verified.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.