-
-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
[WIP] [API] add ReactionSummary to Commit and Issue #9497
Conversation
055142d
to
e0fd483
Compare
e0fd483
to
1113784
Compare
Codecov Report
@@ Coverage Diff @@
## master #9497 +/- ##
==========================================
- Coverage 42.60% 42.59% -0.01%
==========================================
Files 673 673
Lines 73862 73877 +15
==========================================
+ Hits 31470 31471 +1
- Misses 37275 37313 +38
+ Partials 5117 5093 -24
Continue to review full report at Codecov.
|
I still think it should same as github with only counts:
|
@lafriks the problem is that github's responce don't allow custom reaction should i rename the field from |
Why wouldn't it allow custom reactions? Pretty much it would not allow only reactions with name |
dont think this is a nice format to parce! @lafriks as far as I understand it's a section for defined fields ... so you cant simply itterate throu :( |
Also I think that returning all users is too verbose, let's say there will be 1000 likes for issue or comment, for summary we should return only counts and if users are needed than we already have api for that |
It's dictionary ;) |
@lafriks update #9497 (comment) |
This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 months. Thank you for your contributions. |
no stale - |
rev: #8313 (comment)
reaction_summary
is nil or:function itself
exposed for issues
exposed for issue_comments (should but not working
dont return user -> only count emojy by type