GraphQL API

Comentarios

5 comentarios

  • Neztore
    Discord's API is based around two core layers, a HTTPS/REST API for general operations,...

    - Discord's API Documentation

     

    I'm sorry but it doesn't make technical sense to add an additional API purely because you don't like REST. It'd be difficult to maintain and make stuff a lot more difficult on their end. Just use the brilliant API that is already available :)

     

    Source:

    https://discordapp.com/developers/docs/reference#api-reference

    2
    Acciones de comentarios Permalink
  • Killy

    updated

    0
    Acciones de comentarios Permalink
  • Killy

    updated again

    0
    Acciones de comentarios Permalink
  • yaboired

    It's so much more work to maintain two APIs than it is to maintain just one, and it'd only go to waste. I seriously doubt there'd be a significant enough amount of users to justify maintaining an entire second API; the popular libraries that already exist would have to be entirely rewritten to use it.

    0
    Acciones de comentarios Permalink
  • Killy

    Finally a valid concern. Thanks. I'm leaving this, albeit downvoted, request so there is a place to gather all thoughts on the matter.

    I don't think having GraphQL alongside with REST has much of overhead. I think it will be easily justified once the Discord developers find a use of it's flexibility for themselves. Although I haven't had an experience of supporting it by myself - dunno if my expectation of it is too optimistic or not.

    I believe it won't take long for actively supported bot libraries to expose new API endpoints if there are quality GraphQL libraries available for the language they are written in.

    0
    Acciones de comentarios Permalink

Iniciar sesión para dejar un comentario.