From b1529d30bf47d4b0cb3bfdfd53f1cdab596644e9 Mon Sep 17 00:00:00 2001 From: sharils <3063067+sharils@users.noreply.github.com> Date: Sat, 31 Oct 2020 16:39:49 +0800 Subject: [PATCH 1/2] Reduce confusion about the query component MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The query component has never been mentioned in the page, to reduce confusion, a link to its page would explain that it’s deprecated --- docs/source/data/queries.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/source/data/queries.mdx b/docs/source/data/queries.mdx index 2cc4b40e462..31b9ef2f267 100644 --- a/docs/source/data/queries.mdx +++ b/docs/source/data/queries.mdx @@ -171,7 +171,7 @@ We've already seen that the `useQuery` hook exposes our query's current loading Let's return to our refetching example from the previous section. If you click the refetch button, you'll see that the component doesn't re-render until the new data arrives. What if we want to indicate to the user that we're refetching the photo? The `useQuery` hook's result object provides fine-grained information about the status of the query via the `networkStatus` property. To take advantage -of this information, we set the `notifyOnNetworkStatusChange` option to `true` so our query component re-renders while a refetch is in flight: +of this information, we set the `notifyOnNetworkStatusChange` option to `true` so our [query component](../api/react/components/ "Components - Client (React) - Apollo GraphQL Docs") re-renders while a refetch is in flight: ```jsx:title=index.js import { NetworkStatus } from '@apollo/client'; From b55ae84194d5934518455d5aa1c415922f141fe4 Mon Sep 17 00:00:00 2001 From: "John P. Vajda" Date: Fri, 20 May 2022 15:48:41 -0600 Subject: [PATCH 2/2] empty commit to kick off checks