Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

rating counts do not include post-webstore-upgrade ratings #8

Closed
hansifer opened this issue Nov 4, 2011 · 4 comments
Closed

rating counts do not include post-webstore-upgrade ratings #8

hansifer opened this issue Nov 4, 2011 · 4 comments

Comments

@hansifer
Copy link

hansifer commented Nov 4, 2011

The new web store is using new xhr requests to pull extension detail and reviews. I'm thinking the old calls (also currently leveraged by MyExtensions) are likely on the chopping block:

http://chrome.google.com/reviews/json/lookup
http://chrome.google.com/reviews/json/search

For the time being, however, non-Chrome browsers seem to be targeting the old web store, so I guess as long as that's true the calls are safe from extinction... :s

Anyway, I haven't searched exhaustively, but we could be losing the API for rating breakdowns. The current calls don't seem to carry that payload:

https://chrome.google.com/webstore/ajax/detail
https://chrome.google.com/reviews/components

The "detail" call, however, does carry the version #, so in theory one wouldn't have to resort to screen scrape for that.

Personally, I think the rating breakdown is useful for users, so hopefully Google decides to publish it one way or another.

Cheers,
Hans

@hansifer
Copy link
Author

hansifer commented Nov 4, 2011

I meant to add: the current "detail" call does carry the correct total rating count (old web store + new)

@neocotic
Copy link
Contributor

neocotic commented Nov 4, 2011

I've created a patch which takes all the current details from https://chrome.google.com/webstore/ajax/detail instead of scraping the details page, so the version is available again.

I see that this response also contains the number of ratings and average rating which can be accessed in getMeta with my changes using response[1][0][22] and response[1][0][12] respectively.

I agree that the rating breakdown is a nice feature and that that information does not exist in this response. However, I see no evidence that this API is being deprecated and/or removed. What gave you that idea?

Part of my changes is renaming "comment" to "review" but I didn't change anything to do with the API as I better get back to doing my actual job ;P

@hansifer
Copy link
Author

hansifer commented Nov 4, 2011

Once the old web store inevitably becomes inaccessible, there's no reason for Google to keep these calls around. They're not part of any official API, as far as I am aware. Based on that, my thinking is that it's safer to assume they will be deprecated rather than not.

I realize that's a moot point for ratings breakdown since there's currently no alternative, but porting ave rating and rating count is probably a good idea. Otherwise, MyExtensions is just perpetually reporting the static Oct 25 snapshot of these values.

Thanks for your contributions to this extension. I love its utility and use it every day, so your work thus far is much appreciated.

Cheers,
Hans

@neocotic
Copy link
Contributor

I've made an attempt to update the ratings in #13. Hopefully, this will resolve this problem and this can be closed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants