The Apollo extension for Chrome is also awesome. It needs to display errors better but it is already very essential.
Apollo Client 1.0: A flexible, community-focused JavaScript GraphQL client
71–80 of 81 posts
Re: Apollo Client 1.0: A flexible, community-focused JavaScript GraphQL client
#72Re: Apollo Client 1.0: A flexible, community-focused JavaScript GraphQL client
#73Hey, Sashko from the Apollo team here - we're excited to keep improving Apollo Client and build more awesome tools for GraphQL development! If you're excited about this space and want to work on open source and also commercial products for GraphQL, we're actively hiring for a variety of positions: http://jobs.meteor.com/
Cheers...
Re: Apollo Client 1.0: A flexible, community-focused JavaScript GraphQL client
#74Re: Apollo Client 1.0: A flexible, community-focused JavaScript GraphQL client
#75We use Apollo for the http://expo.io/ client and have found it to be extremely pleasant to use. I love how flexible it is too -- you can use it for weird things like building an ORM layer for SQLite. For example: https://github.com/brentvatne/apollo-sqlite-experiment/blob/... -- the queries here go through a custom NetworkInterface which use a pretty simple graphql resolver ( https://github.com/brentvatne/apollo-sqli…
What is the expo.io client? The site you linked has a broken certificate and then just replies "default backend - 404".
Re: Apollo Client 1.0: A flexible, community-focused JavaScript GraphQL client
#76Earlier quoted context omitted.
I'm kind of hoping that nesting resources becomes a non-issue in the future once HTTP/2 is widespread. Ideally you don't ever nest resources. With HTTP/2 the overhead of additional requests can be significantly lower, and you get the benefit of using client cache. This becomes pretty powerful once cache digests land, so a HTTP/2 REST service can just proactively push only the resources to the client that it has an (u…
HTTP/2 won't save you round-trips as you follow REST hypermedia links.
this assumes you have high confidence the client will actually request those links (or you can afford to send them even with low confidence) but you can use media types or query parameters to mitigate that