Support skipToken with useQuery

[jerelmiller]

Closes #11524

Add support for skipToken with useQuery.

[changeset-bot]

🦋 Changeset detected

Latest commit: 89ca02a

The changes in this PR will be included in the next version bump.

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[apollo-librarian]

✅ Docs preview ready

The preview is ready to be viewed. View the preview

File Changes

0 new, 2 changed, 0 removed

* (developer-tools)/react/(latest)/api/react/skipToken.mdx
* (developer-tools)/react/(latest)/data/queries.mdx

Build ID: ccca34baa4b138bd8f97e246
Build Logs: View logs

URL: https://www.apollographql.com/docs/deploy-preview/ccca34baa4b138bd8f97e246

[jerelmiller]

We still want this as a patch correct?

[phryneas]

Maybe we add a little bit more prose to explain why we do it as a patch (variables are hard to use with the new types otherwise) to the changeset, but yeah, I think this can count as a fixup of an oversight.

[pkg-pr-new]

npm i https://pkg.pr.new/apollographql/apollo-client/@apollo/client@12895

commit: 89ca02a

[jerelmiller]

May need updating if we don't get this in 4.0.4

[github-actions]

size-limit report 📦

Path	Size
import { ApolloClient, InMemoryCache, HttpLink } from "@apollo/client" (CJS)	42.82 KB (0%)
import { ApolloClient, InMemoryCache, HttpLink } from "@apollo/client" (production) (CJS)	37.8 KB (0%)
import { ApolloClient, InMemoryCache, HttpLink } from "@apollo/client"	32.66 KB (0%)
import { ApolloClient, InMemoryCache, HttpLink } from "@apollo/client" (production)	26.85 KB (0%)
import { ApolloProvider } from "@apollo/client/react"	5.91 KB (0%)
import { ApolloProvider } from "@apollo/client/react" (production)	994 B (0%)
import { useQuery } from "@apollo/client/react"	7.35 KB (+1.89% 🔺)
import { useQuery } from "@apollo/client/react" (production)	2.39 KB (+6.08% 🔺)
import { useLazyQuery } from "@apollo/client/react"	7.11 KB (0%)
import { useLazyQuery } from "@apollo/client/react" (production)	2.16 KB (0%)
import { useMutation } from "@apollo/client/react"	6.47 KB (0%)
import { useMutation } from "@apollo/client/react" (production)	1.52 KB (0%)
import { useSubscription } from "@apollo/client/react"	6.79 KB (0%)
import { useSubscription } from "@apollo/client/react" (production)	1.81 KB (0%)
import { useSuspenseQuery } from "@apollo/client/react"	8.55 KB (0%)
import { useSuspenseQuery } from "@apollo/client/react" (production)	3.63 KB (-0.03% 🔽)
import { useBackgroundQuery } from "@apollo/client/react"	8.33 KB (+0.02% 🔺)
import { useBackgroundQuery } from "@apollo/client/react" (production)	3.4 KB (+0.03% 🔺)
import { useLoadableQuery } from "@apollo/client/react"	8.3 KB (0%)
import { useLoadableQuery } from "@apollo/client/react" (production)	3.39 KB (0%)
import { useReadQuery } from "@apollo/client/react"	6.6 KB (0%)
import { useReadQuery } from "@apollo/client/react" (production)	1.65 KB (0%)
import { useFragment } from "@apollo/client/react"	6.66 KB (0%)
import { useFragment } from "@apollo/client/react" (production)	1.71 KB (0%)

[phryneas]

This one is so weird since technically the variables are gone now.

How should we handle this if you go from passing in variables to skipToken - should refetch refetch with the previous variables, or with no variables?

This might need a bit of thought.

[jerelmiller]

Discussed in person. Since useSuspenseQuery and useBackgroundQuery allow refetch with skipToken, we are going to leave this the same. This could mean you see runtime errors if refetching with required variables.

[jerelmiller]

Before merge, update the changelog description