apollo-client-devtools VS apollo-angular

This call creates canonical field allTodos on the root Query type. We can confirm this by opening apollo devtools and viewing the 'cache' tab.

People don't understand how their code can mess up others in unexpected ways. A few weeks ago my youtube just stopped working. Turns out, a change made to the apollo-graphql extension caused window.process to be readonly and youtube's code was not expecting that: https://github.com/apollographql/apollo-client-devtools/issu...

I know this isn't a dependency issue, but it's a great example of why things like semver don't work perfectly in practice. It's hard to figure out what the effects of your code really are in the end. You might assume a change is minor when it really is major. I wish programming languages could figure out what the version change should be for a given code change.

Do you perhaps use chrome and have apollo client dev tools installed? They break import maps, which breaks the site, see here: https://github.com/apollographql/apollo-client-devtools/issues/464

It's so weird that this seems like a common use case but across the 3 channels I've asked (also asked on the official Apollo Spectrum chat & SO) it's radio silence beyond your reply! To add insult to injury, Apollo devtools was updated over the weekend and broke for v2 clients! Argh!!

Case in point: Apollo Angular (GraphQL) does the basics of what you want, but it does so much more that its existence is justified...yet you still have to use RxJS with it.

Not that I know of. But here are a few things that may be of interest.

Redwood's GraphQL API is built on Yoga (we collaborate tightly with The Guild) — https://www.graphql-yoga.com You just need a GraphQL Client, which The Guild already has an option ready for you https://apollo-angular.com (Note: Apollo or other clients fine as well.)

Here's an example "How To" about connecting Next (React) with Redwood: https://community.redwoodjs.com/t/how-to-connect-a-next-js-f...

I'm a co-founder of Redwood and help lead the project so I can say as a matter of fact we a highly collaborative and enjoy (and support) exploratory projects. It's a priority for us to better demonstrate the power of Redwood's API through examples. If you'd be interested in digging in collaboratively with the community, I can help connect the dots. Just kick things off over here and tag me @thedavidprice: https://community.redwoodjs.com

No pressure at all! Just wanted you to know the invitation is open. Anytime.

Apollo Angular

TLDR: We’ve built a multiplayer shooter and used Apollo’s GraphQL subscriptions to keep game state in sync at a very high frequency. Here’s our impressions! Tools used: Angular-cesium, Apollo Angular, CesiumJS, Angular Go Play: geo-strike.com