Hacker News Reader

Comment by CharlieDigital | Hacker News Reader

Article says that it doesn't apply to the GQL API. Wonder what this means long term for the GQL interface.

Author here! We still love our GraphQL API, and REST and GraphQL continue to evolve in parallel.

We’re just aware that GraphQL is pretty different, so if we want versioning there, we’ll need to tackle it differently. (On top of that, GraphQL has some nice primitives that come for free, like deprecated fields.)

Would be curious to hear though how GitHub plans to evolve the GraphQL API. From the recent almost unannounced removal of the GraphQL package API one can get the impression that it’s safer to use the REST APIs.

> recent almost unannounced removal of the GraphQL package API

i missed this, is there a canonical source to learn more?

Author here! Here's the link to that announcement: https://github.blog/changelog/2022-08-18-deprecation-notice-...

Author here! At the moment, we allow teams across GitHub to make their own decisions on REST vs. GraphQL. Some teams are investing heavily in GraphQL (e.g. for the new GitHub Projects), whereas others are opting for REST. That said, we do want to firm up our guidance internally and communicate more clearly to the world how we think about REST and GraphQL.

The inconsistency is quite annoying as a user. Particularly new projects is leaving a bad taste because its the only thing I’m aware if that’s GraphQL only and there is little communication about a REST API, yet the UI uses an internal REST API.

I definitely feel your pain and, unsurprisingly, it's something we hear very regularly from users. We're working on it.

Reply on news.ycombinator.com