Closed Bug 894589 Opened 12 years ago Closed 12 years ago

API consumers should be able to remove apps from a collection

Categories

(Marketplace Graveyard :: API, defect, P2)

x86
macOS
defect

Tracking

(Not tracked)

RESOLVED FIXED
2013-08-13

People

(Reporter: chuck, Assigned: chuck)

References

Details

(Whiteboard: p=1 [qa+])

API consumers should be able to remove applications from a collection at a unique endpoint. This endpoint should be protected by the Apps:Collections permission created in bug 894425.
Depends on: 896647
Priority: -- → P2
Assignee: nobody → charmston
Added Flue API endpoint: curl -X POST 'http://localhost:5000/api/v1/rocketfuel/collections/<collection_slug>/remove_app/' -d 'app=<app_id>' https://github.com/mozilla/flue/commit/c1a0f30 P.S. We probably want the ability to take a comma-delimited list (or a JSON-formatted list) of app_ids - to avoid having to do multiple HTTP requests. We can sync up about this, and I can adjust Flue. Holler at your boi!
When would we want to add or remove multiple apps at once? The mocks in bug 889556, comment 2 seem to imply that everything would happen 1 request at a time.
Landed here: https://github.com/mozilla/zamboni/commit/70193bdb42e431b003e2a496a79390847f5a4740 STR: 1) Create a collection using the STR in bug 894456. 2) Add an app to the created collection in a separate request using the endpoint outlined here: http://firefox-marketplace-api.readthedocs.org/en/latest/topics/rocketfuel.html#post--api-v1-rocketfuel-collections-%28int-id%29-add_app- 3) Remove the same app from the created collection in a separate request using the endpoint outlined here: http://firefox-marketplace-api.readthedocs.org/en/latest/topics/rocketfuel.html#post--api-v1-rocketfuel-collections-%28int-id%29-remove_app- 3) A successful attempt's response will contain a JSON representation of the collection with an `apps` property that does not include the URL of the removed app.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Whiteboard: p=1 [qa+]
Target Milestone: --- → 2013-08-13
You need to log in before you can comment on or make changes to this bug.