fetchMore with fetchPolicy: "no-cache" makes two requests about apollo-client HOT 5 CLOSED

I've got a failing test written for this in #11974. I've discovered some deeper issues with this as well that I think we need to discuss as a team, so I'm going to leave this in draft for now. Thanks for reporting the issue!

from apollo-client.

Hi there @username14415 👋 Unfortunately, without a reproduction there's not much I do to help. If you're able to create one, I'd be happy to take a look.

from apollo-client.

@alessbell

const GET_MESSAGES = gql query GetMessages($slug: String!, $offset: Int) { getMessages(slug: $slug, offset: $offset) { id content } }

const { fetchMore } = useQuery(GET_MESSAGES, { fetchPolicy: "no-cache", variables: { slug: "example-slug } });
const fetch = await fetchMore({ variables: { offset: 123 }});

Using fetchMore with "fetchPolicy: "no-cache" shows 2 requests. The requests are visible on the backend.
The first request has my own set variables (in this case offset: 123 and default variable slug). The second request has only default variable (slug).

from apollo-client.

Hey @username14415 👋

I believe I'm able to reproduce this. Check out this reproduction which shows the multiple requests. I see the 2nd request kicked off after the first resolves. It helps to open this up the app in a separate window: https://y37kx4-3000.csb.app/. For whatever reason console logs are duplicated in the split view version giving a false sense of what is happening.

from apollo-client.

Do you have any feedback for the maintainers? Please tell us by taking a one-minute survey. Your responses will help us understand Apollo Client usage and allow us to serve you better.

from apollo-client.