Closed
Bug 560623
Opened 14 years ago
Closed 14 years ago
New api method for the discovery pane: /api/list/top/...
Categories
(addons.mozilla.org Graveyard :: Public Pages, defect, P1)
Tracking
(Not tracked)
RESOLVED
FIXED
5.10
People
(Reporter: jbalogh, Assigned: davedash)
References
()
Details
(Whiteboard: [z])
From the spec: This module lists the top 5 add-ons by average daily users over the past week. Add-ons shown in this list should always been compatible with the user's application, which means we should filter server-side and only send add-ons that are compatible with the application, OS, and browser version. We do all this for list/featured, so sticking this in the api seems like the right way to go.
Reporter | ||
Comment 1•14 years ago
|
||
It would be nice to work with JSON instead of XML here.
Comment 2•14 years ago
|
||
(In reply to comment #1) > It would be nice to work with JSON instead of XML here. That's bug 543561 and, depending on how long it will take, shouldn't block this. Davedash, can you estimate how long that would take?
Reporter | ||
Comment 3•14 years ago
|
||
(In reply to comment #2) > (In reply to comment #1) > > It would be nice to work with JSON instead of XML here. > > That's bug 543561 and, depending on how long it will take, shouldn't block > this. Right, it can't block this, but json would be really really nice. I'm also planning to use /api/list/featured, so JSON all over would be good.
Comment 4•14 years ago
|
||
(In reply to comment #3) > (In reply to comment #2) > > (In reply to comment #1) > > > It would be nice to work with JSON instead of XML here. > > > > That's bug 543561 and, depending on how long it will take, shouldn't block > > this. > > Right, it can't block this, but json would be really really nice. I'm also > planning to use /api/list/featured, so JSON all over would be good. I want to use it for /top-tags too
Assignee | ||
Comment 5•14 years ago
|
||
I can get the /list/by_adu call tomorrow, and the JSON API before freeze, if not before the end of this week.
Status: NEW → ASSIGNED
Assignee | ||
Comment 6•14 years ago
|
||
470e893..114ac35 master -> master
Status: ASSIGNED → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Comment 7•14 years ago
|
||
What URLs should QA be testing, here? Besides, that is: https://preview.addons.mozilla.org/z/en-US/firefox/api/1.5/list/top https://preview.addons.mozilla.org/z/en-US/firefox/api/1.5/list/featured https://preview.addons.mozilla.org/z/en-US/firefox/api/1.5/list/top-tags For QA: commit is http://github.com/jbalogh/zamboni/commit/114ac35.
Assignee | ||
Comment 8•14 years ago
|
||
api/1.5/list/by_adu/* <- this is that stupid format that we use for the other APIs also for list api's you can tack on ?format=json cheers
Updated•14 years ago
|
Flags: in-testsuite?
Flags: in-litmus?
in-litmus+: https://litmus.mozilla.org/show_test.cgi?searchType=by_id&id=12081 : New api method for the discovery pane
Flags: in-litmus? → in-litmus+
Updated•8 years ago
|
Product: addons.mozilla.org → addons.mozilla.org Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•