-
Notifications
You must be signed in to change notification settings - Fork 791
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
Reactions #25
Comments
Since we are moving to GraphQL, this is worth taking a look at https://developer.github.com/v4/reference/mutation/addreaction/ Also, getting the reactions seems also somewhat intuitive with GraphQL. Altho the end result seems a bit messy, but I am sure we can work with it! |
That looks really nice @housseindjirdeh! |
Thanks @RolfKoenders :) Nice thank you @SammyIsra - with REST things were quite messy and I really think this can be something we can integrate after we have GraphQL integrated. |
That being said - looking at the documentation for API v4 I don't see a mention of reactions being in preview mode like it is in the REST docs. @SammyIsra do you know if we need a preview URL or something of that sort to access reactions with GraphQL? |
@housseindjirdeh No developer preview header is needed for reactions in API v4, it's all implemented and standard 👍 |
OMG OMG OMG Time to make the move to GraphQL :) |
If it's okay with everyone - I'll like to take this on and tackle it over Christmas break and start my first stab at using GraphQL :) |
👏 1.5 is going to be a good one! |
So I spent a bit of time some while ago working on adding reactions. This is all in the
with-reactions
branch of the repo. Keep in mind this is a much older branch and there have been a lot of changes since than onmaster
, but I feel we can port our logic from there when we're ready.This is what I had working:
You'll notice Slack inspiration there :P
An important thing to point out is that the Reactions APIs are still in development preview. Definitely worth discussing if we wouldn't mind including it now and changing it in the future or if that's not the safest option just yet.
Looking forward to having this rolled out eventually. Discussions/contributions are always welcome :)
The text was updated successfully, but these errors were encountered: