@d12 & @gjtorikian
A big thing for us is that we are currently translating between REST webhooks and GraphQL data shapes. We have views that hydrate their data from GraphQL, but then to keep them up to date in realtime we have to have a webhook receiver who’s sole purpose is to receive GitHub webhooks (in REST form), translate the data into the GraphQL schema, and then republish them over our own websockets. Every time we build something new on GraphQL, we have to build the translation layer for the webhooks. It is not the end of the world, but it is quite error prone and fairly burdensome for your integrators.
Also, it makes it hard for some of your integrators to know how to invest in the GitHub ecosystem right now. It appears as though GraphQL is the recommended path going forward; however, if we do use GraphQL, we end up needing things like our translator to fill in the gaps. It is one thing for it to be an interim thing, but it is discouraging to hear there is no plan to make GraphQL a stand alone solution for integrators.
Hopefully that’s helpful. I know we probably use the GitHub GraphQL API in some unique ways as compared to other integrators. It is definitely a pain point we feel though.