Currently, PostMixin deserializes "likes/count" into the likeCount property on the Post object. But, as described in
SOCIALFB-33, sometimes you get back a count of likes and sometimes you get a list of users who have liked the post. While SOCIALFB-33 fixes a NPE when the "count" field isn't in the returned JSON, this issue seeks to fetch the users who have liked an object as well as the count (assuming the data is available).
The tricky part of this issue is reconciling the discrepancy between the value of "count" and the number of items in the "data" list. For example...
- https://graph.facebook.com/40796308305_10150394134258306 will fetch JSON for a post whose "likes/count" field indicates 3 users have liked the post, but whose "likes/data" only contains a single user reference.
- https://graph.facebook.com/40796308305_10150394134258306/likes will fetch JSON for the post's likes, with 3 users in the "data" field.
- Viewing that same post on the Coca-Cola page on Facebook shows that, in fact, 3 people have liked the post.
It's easy enough to fetch the users who have liked a post, but before implementing this, I'd like some explanation of why the "data" field may not contain all entries. It doesn't seem to be a matter of paging, as there's no need to page any less than 3 items. I've asked about this on Facebook's StackOverflow site: http://facebook.stackoverflow.com/questions/8043467/difference-between-a-posts-likes-count-and-the-likes-data