API: handle reactions to comments

[6543]

GET     /repos/{owner}/{repo}/issues/comments/{id}/reactions
PUT     /repos/{owner}/{repo}/issues/comments/{id}/reactions
DELETE  /repos/{owner}/{repo}/issues/comments/{id}/reactions

[6543]

GitHub docu https://developer.github.com/v3/issues/comments/#reactions-summary
think we can do better

[6543]

@mmarif4u what is earyer to process:

for GET /repos/{owner}/{repo}/issues/comments/{id}/reactions

Either

[
  {
    "id": 0,
    "username": "6543",
    "reaction": "heart",
  },
  {
    "id": 4,
    "username": "6543",
    "reaction": "laugh",
  },
  {
    "id": 8,
    "username": "mmarif",
    "reaction": "laugh",
  },
  {
    "id": 10,
    "username": "user1",
    "reaction": "confused",
  }
]

Or

[
  {
    "reaction": "heart",
    "users": [ "6543" ]
  },
  {
    "reaction": "laugh",
    "users": [ "6543", "mmarif" ]
  },
  {
    "reaction": "confused",
    "users": [ "user1" ]
  }
]

PS: i dont like to send whole User.APIFormat() user this would generate to mouch overhead

[guillep2k]

[
  {
    "reaction": "heart",
    "users": [ "6543" ]
  },
  {
    "reaction": "laugh",
    "users": [ "6543", "mmarif" ]
  },
  {
    "reaction": "confused",
    "users": [ "user1" ]
  }
]

Is better: more concise, no ids exposed.

[mmarif4u]

I agree with @guillep2k, that is the right way to do it. 👍

[6543]

PUT / DELETE use as body

{
    "reaction": "heart",
    "users": [ "6543" ]
 }

I could make it eaven mor simpler by just allow a string to be send or

"reaction": "heart"

but i leave it open so admins have an API to send ractions for other users/bots... too

[zeripath]

Don't forget Sudo allows an admin to act like any other user - so you should only add that if you're going to allow the admin to set multiple user's reactions.

[lafriks]

imho we should follow GitHub API compatibility:
https://developer.github.com/v3/reactions/

Link above is just reaction counts by type in issue details API

[6543]

@lafriks @techknowlogick one downside:

consider a issue with 15 comments -> each had ~ 10 reactions
-> api return user information in the worst case 150 times (dedundancy)
and if there all other users we still load a huge amount of user information wich isnt used ...
and if an app like to load more about a user it still kan get it by its name

I'm thinking about mobile conection ...

@lafriks add more fields beside the user{} can be usefull but should i expose the reaction ID (-> @guillep2k)?

[6543]

proposal2

GET /repos/{owner}/{repo}/issues/comments/{id}/reactions
consume: null
return:

[
  {
    "user": "octocat",
    "content": "heart",
    "created_at": "2016-05-20T20:09:31Z"
  },
  {
    "user": "6543",
    "content": "heart",
    "created_at": "2017-10-20T20:09:31Z"
  }
]

PUT/DELETE /repos/{owner}/{repo}/issues/comments/{id}/reactions
consume:

content: "heart"

return:

[
  {
    "user": "octocat",
    "content": "heart",
    "created_at": "2016-05-20T20:09:31Z"
  }
]

[lafriks]

I don't agree as most probably you will still want to have user avatar url, user url, we do return this format in all other api, so I would not like this to be different. Reaction summary (counts by type) you will already have them in issue/pr/comment API. These are details so you really need to request them rarely - when you really want to know exact details

[6543]

@lafriks
GET /repos/{owner}/{repo}/issues/{index} as no reaction info
GET /repos/{owner}/{repo}/pulls/{index} also

a GET /repos/{owner}/{repo}/issues/comments/{id} do NOT exist!
and GET /repos/{owner}/{repo}/issues/comments has no reaction info

this is same at GET /repos/{owner}/{repo}/issues/{index}/comments