Nice to see a lot of improvements! I spent some time today to upgrade an app from Apollo 1.9. I ran into some issues if you use TypeScript.
The typings used in the library are not listed as dependencies, so I had to manually install them. This may get fixed soon (https://github.com/apollographql/apollo-link/pull/171), though I had to install three @types packages: graphql, lodash.flowright, and zen-observable.
The ApolloProvider parameter for client is also broken: https://github.com/apollographql/apollo-client/issues/2212
Also, `data.loading` still gets stuck to true. See https://github.com/apollographql/apollo-client/issues/1186, though this issue has repeatedly been opened and closed.
We tried Apollo in its very early stage, the code complexity and the hard to debug object cache management drove us away. We are quite happy with some simple combination of raw fetch and mobx.
Will definitely take another look at the v2!
Is Apollo good? I feel like I’ve been aware of their existence for a long time — they have a large marketing presence but I don’t actually have any idea what it is ... there’s a server for making graphql servers and a client for doing ...??? I know they have tools for compiling graphql queries into various typed language interfaces which I have lusted for.
I feel like every blog post of theirs I’ve ever clicked is high percentage marketing and not a lot of focused explanation ...
They have a tough communication nut to crack — they have to sell to people who’ve never heard of graphql, to people who’ve lusted after the vision communicated very clearly by Facebook for graphql and relay, to people using redux and the disarray of different mechanisms for straddling the various in practice divides between local and server state.
Being able to map rest apis into graphql apis on the browser side seems like a nice migration strategy but there still seems like something missing to me to feel like I know what the value proposition of the Apollo Client is ...
Are there any good live demo style introductions to Apollo — something gripping like the original redux conference demo[1] ...?
We're using Apollo v1 and tried the upgrade to v2 a few weeks ago. It was hard and buggy to replicate what we had (subscriptions, batched requests, polling requests). We reverted to v1 in the end because if the bugs and the complexity.
What really hurts us in v1 is the error handling. When querying a collection of items, if 1 item has an error, only the error is returned with no payload.
Hopefully all of these will get resolved the coming months.
Congrats to the Apollo team! A ton of work went into this
Apollo link rest looks handy. Resolving it server-side would be even better. Is it more for client-side resolution?
+1 to Apollo. It’s been amazing so far. No real hurdles. There’s maybe a few tricks to figure out how to manage auth but it’s not too bad. Good stuff!
Apollo's set of tools are some of my favorite programming libraries/tools ever. They _just work_ and more often than not I have thought of an feature that turned out that they already had.
Congrats of releasing Apollo Client 2.0, can't wait to try it out in production.
Sweet! I've been waiting for this! I've yet to tinker much with 2.0 though... Is there a nice way to debug state similar to Redux DevTools (now that Apollo no longer uses Redux)? Being able to use Redux DevTools is one of my favorite features about Apollo.
Apollo is amazing! Have been using it since the start. But too bad there is no working vue version for 2.0 yet. Really hoping for Vue to become officially handled by the ApolloTeam.
> We have also rewritten a large portion of the documentation for using Apollo
Unfortunately it seems like the core API docs are still woefully out of date and full of broken links: http://dev.apollodata.com/core/
Despite that, my experience with Apollo in general has been good. I maintain the Ember addon for it, and I find I'm much happier and more productive with Apollo Client + GraphQL than I ever was using ember-data + JSON API.
https://github.com/bgentry/ember-apollo-client