Closed
Bug 936130
Opened 11 years ago
Closed 11 years ago
Add submission API step to content ratings
Categories
(Marketplace Graveyard :: API, defect, P1)
Tracking
(Not tracked)
RESOLVED
FIXED
2013-12-03
People
(Reporter: robhudson, Assigned: robhudson)
References
Details
Analogous to us accepting a submission_id and security_code to look up an IARC content rating, we should accept one via the submission API to do this as well so apps can continue to be submitted via API.
Comment 1•11 years ago
|
||
If they aren't there, I guess we should return a 4xx? Definitely should add this requirement to the docs.
Updated•11 years ago
|
Assignee: nobody → ashort
Comment 2•11 years ago
|
||
Relevant code: https://github.com/mozilla/zamboni/blob/master/mkt/developers/forms.py#L1088
Assignee | ||
Comment 3•11 years ago
|
||
There's actually 2 parts to this... 1. Update the "status" API to know about content ratings and if an app can be set to PENDING. I believe this is already done (or in a pull request) as part of the move to DRF. 2. Add a new API to submit an IARC submission ID and security code to fetch the content ratings from IARC. I can take item 2.
Assignee | ||
Updated•11 years ago
|
Assignee: ashort → robhudson.mozbugs
Assignee | ||
Comment 4•11 years ago
|
||
https://github.com/mozilla/zamboni/commit/0293da6 To verify, use the submission API to submit an app, including the IARC content ratings and verify the content ratings show up on the app resource API and that the app can be set to PENDING using the status API. See: http://firefox-marketplace-api.readthedocs.org/en/latest/topics/submission.html
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Target Milestone: --- → 2013-12-03
You need to log in
before you can comment on or make changes to this bug.
Description
•