GitHub announcements: Marketplace, Apps and GraphQL API

Post by nailer » Tue, May 23, 2017, 11:18 AM UTC

philstu wrote: post #78

nailer wrote: post #16

Earlier quoted context omitted.

The main thing vs REST is that it fixes the 'overlapping data in resources' issue. Want a timeline of tweets? Well you'll also want avatars to display, and you probably don't want that in a separate resource (because of multiple requests), so both /tweets and /users/userid will give you avatar details. It's a bit messy. In graphQL there's one resource and you query it to tell you what you want.

Hey! I cover that a bit ni a followup blog post :) https://blog.runscope.com/posts/you-might-not-need-graphql tl;dr: maybe you want OData, JSON-API, or one of the many other standards or practices that solve this simple problem as their super-set of functionality on top of the networking principles of REST. Using GraphQL for this alone is rather nuclear, as you gain a lot with GraphQL but lose other stuff.

Post by user15672 » Thu, May 25, 2017, 2:10 PM UTC

nikon wrote: post #86

user15672 wrote: post #61

Earlier quoted context omitted.

What's the point in GitHub creating yet-another-CI-tool? Travis and Circle CI have had good integrations for years and work very well.

Cost?

Post by nikon » Mon, May 29, 2017, 12:43 PM UTC

user15672 wrote: post #163

nikon wrote: post #86

Earlier quoted context omitted.

Cost?

Circle CI works well on their free tier, so no, not cost.