Closed
Bug 894643
Opened 11 years ago
Closed 11 years ago
API consumers should be able to add collections to a region/page pair
Categories
(Marketplace Graveyard :: API, defect, P2)
Tracking
(Not tracked)
RESOLVED
FIXED
2013-08-27
People
(Reporter: chuck, Assigned: mat)
References
Details
From the publishing tool, publishers will be able to add an arbitrary number of collections and featured applications to a region (country + operator)/page (category + homepage) pair. To do this, we need an endpoint that allows users to add collections to a region/page pair. This endpoint should be protected by the Apps:Publisher permission created in bug 894425.
Reporter | ||
Updated•11 years ago
|
Assignee: nobody → charmston
Reporter | ||
Updated•11 years ago
|
Assignee: charmston → mpillard
Comment 1•11 years ago
|
||
Flue API endpoint @ /api/v1/rocketfuel/collections/ https://github.com/mozilla/flue/commit/8498d80
Comment 2•11 years ago
|
||
Should we be adding collections to a region/carrier/collection_type pair? Or should we be having a separate collection for each region/carrier/collection_type? I'm thinking the latter. It'd make bug 894591 the same as 894638, etc. There are several dupes we could dupe if we go this route.
Assignee | ||
Comment 3•11 years ago
|
||
It looks like all that will be left to do once bug 903489 is done is to determine, code and test the relevant unique constraints.
Assignee | ||
Comment 4•11 years ago
|
||
So, unique constraints are going to be tricky, because we'd want constraints that depend on the value for another field. So we are going to have to do this manually: <cvan> (...) let's just make sure the admin doesn't create more than one category/region/carrier combination for operator shelves+featured apps Worst case scenario, an extra collection would be created, we need to make sure that a) the consumer pages only display the first one b) the admin displays all of them to be able to edit and remove the extra one.
Assignee | ||
Updated•11 years ago
|
Status: NEW → ASSIGNED
Assignee | ||
Updated•11 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Target Milestone: --- → 2013-08-27
Assignee | ||
Comment 5•11 years ago
|
||
Fixed in https://github.com/mozilla/zamboni/commit/f280e892d1ea962641c145ca1ecb2b15236251c7
You need to log in
before you can comment on or make changes to this bug.
Description
•