Duplicate GraphQL queries about next-apollo HOT 9 CLOSED

@wayne530 - Looks like someone got to the bottom of this a couple days ago on the next.js apollo example :) vercel/next.js#8917

I'll look into implementing the fix here as well.

from next-apollo.

Note: Do not be alarmed that you see two renders being executed. Apollo recursively traverses the React render tree looking for Apollo query components. When it has done that, it fetches all these queries and then passes the result to a cache. This cache is then used to render the data on the server side (another React render). https://www.apollographql.com/docs/react/api/react-ssr/#getdatafromtree

from next-apollo.

@colinappnovation thanks for the reply. To be clear, I’m not seeing multiple different queries, I’m seeing exactly two identical graphql queries on a page that in theory should only execute one. By adding a console.log, I verified the server is executing one and the client is executing one. I would expect that if the page is rendered server-side, I would only see a single query by the server, and similarly, if the page is rendered client side, I’d see a single query by the client. Seeing both feels unexpected and certainly could have unintended consequences for mutations.

from next-apollo.

@adamsoffer I'm wondering if you might be able to comment on the "expectedness" of what I'm seeing? Do you see the same thing with your canonical example?

from next-apollo.

That's awesome news, thanks @adamsoffer for the update!

from next-apollo.

Hey @adamsoffer, just checking to see if you have any updates on this?

from next-apollo.

@adamsoffer @wayne530 was this issue resolved ? I face the same issue.

from next-apollo.

@chandan-reddy-k unfortunately, I don’t think it has yet.

from next-apollo.

This should be fixed in v4.0.0

from next-apollo.