This will allow to do more with fewer requests and in a consistent way.
This will solve issues like this: https://support.discordapp.com/hc/en-us/community/posts/360041483031-Bulk-Reactions
You guys downvoters are short-sighted!
I have nothing against REST API. It's simpler and it's already working. GraphQL usually can't replace it completely.
But GraphQL can be introduced gradually alongside with REST API.
And there are good reasons why graphQL was created - there are tasks that it can do better that REST API.
I wrote this request after I wrote complicated code just for mere goal of reading all reactions from a given user under a given message (have to do a separate request for all existing reactions). This is a shortcoming of the existing API. Same for the absence of bulk emoji additions.
These operations should be trivially described in GraphQL. As well as any other stuff that authors of REST API never thought of.
> Bulk adding reactions to use them as buttons is not a use-case of the API we're wanting to support/encourage.
> There are talks internally of adding an API to add buttons - but we don't have any official plans yet.
I've no idea if the plans were solidified in the last two years. So far we just stuck in the situation where slowed down reactions is all we can use.
It probably worth to vote for something like https://support.discordapp.com/hc/en-us/community/posts/360040066771-Embed-Buttons
댓글을 남기려면 로그인하세요.