title: Apollo Client 3: query returns results in Chrome's Network tab, but undefined in my app
body: <p>I am fetching some data using <code>@apollo/client</code> v3. In Chrome's network tab (http results), I can see it returns data and errors (I am not worried about the error, I know why it is right now.):</p>
  <pre><code>{
      data: {workItems: [,…]},…},
      errors: [{message: &quot;Error trying to resolve position.&quot;
  }
  </code></pre>
  <p>However in my app, <code>data</code> returns undefined.</p>
  <p>Here's my client config:</p>
  <pre><code>export const graphqlClient = new ApolloClient({
      cache: new InMemoryCache(),
      link: ApolloLink.from([
          onError(({ graphQLErrors, networkError }) =&gt; {
              if (graphQLErrors) {
                  graphQLErrors.forEach(error =&gt;
                      console.log(
                          `[GraphQL error]: ${JSON.stringify(error, null, 2)}`
                      )
                  )
              }
              if (networkError) {
                  console.log(`[Network error]: ${networkError}`)
              }
          }),
          apolloLink
      ])
  })
  </code></pre>
  <p>And my query:</p>
  <pre><code>gql`
      query WorkItems($ppm: String) {
          workItems(where: { ppm: $ppm }) {
              ...WorkItemKanban
          }
      }
      ${workItemFragment.workItemKanban}
  `
  
  const useWorkItemListDataGraphql = (args: {
      query: DocumentNode
      variables: { parent: string } | { ppm: string }
  }) =&gt; {
      const { variables, query } = args
      const { data, error, loading, refetch } = useQuery&lt;
          { workItems: WorkItem[] },
          { parent: string } | { ppm: string }
      &gt;(query, {
          pollInterval: 180000,
          variables
      })
    
      // data returns undefined, but error shows the same error as in Chrome's network tab
      return { ...data, error, loading, refetch }
  }
  </code></pre>
  <p>I am not sure where to start to identify what goes wrong. Loading the data works when there is no error, but I reckon this is not normal behavior, it should always load the same as I can see in Chrome's tab.</p>