🐛 useQuery doesn't work when there is both a @client directive and a normal query together

How to reproduce the issue:

1. Create a query with both a @client directive (with an alias) and a normal query together, eg:

query GroupsTableQuery($organizationId: ID!) {
  clientOrganization: organization(id: $organizationId) @client {
    planType
  }
  organization(id: $organizationId) {
    groups {
      id
      name
    }
  }
}

1. Use it:

  const { data, loading, error } = useQuery(GroupsTableQuery, {
    variables: { organizationId },
  });

Intended outcome:

• The server correctly returns data with groups, id and name.
• Apollo resolves the @client directive.
• useQuery returns { data } with both clientOrganization and organization.

Actual outcome:

• The server correctly returns data with groups, id and name. ✅
• Apollo doesn’t resolve the @client directive. ❌
• useQuery returns { data } as undefined. ❌

Obs:

If I have two separate queries, everything works as expected (so I know there is nothing wrong with my queries). Eg:

query ClientGroupsTableQuery($organizationId: ID!) {
  clientOrganization: organization(id: $organizationId) @client {
    planType
  }
}

query GroupsTableQuery($organizationId: ID!) {
  organization(id: $organizationId) {
    groups {
      id
      name
    }
  }
}

PS: You might be wondering why I have an organization that’s resolved on the client and another that’s resolved on the server, and this is because we’re slowly migrating our BE to GraphQL, so parts of the data is resolved on the client through our Rest API.

Versions

  System:
    OS: macOS 10.15.5
  Binaries:
    Node: 10.15.3 - ~/.nvm/versions/node/v10.15.3/bin/node
    Yarn: 1.22.4 - ~/.yarn/bin/yarn
    npm: 6.4.1 - ~/.nvm/versions/node/v10.15.3/bin/npm
  Browsers:
    Chrome: 84.0.4147.89
    Edge: 84.0.522.40
    Firefox: 78.0.2
    Safari: 13.1.1
  npmPackages:
    @apollo/client: ^3.0.0-beta.41 => 3.0.0-beta.41
    @apollo/link-error: ^2.0.0-beta.3 => 2.0.0-beta.3

[zmaniacz]

Seeing the same issue on Apollo Client 3.0.2. In my case the query resolves correctly and the graphql call returns correct data when watching the Network tab in dev tools. However, ‘data’ is still returned as ‘undefined’. Removing the field with @client fixes it and have confirmed the @client field I’m using works on it’s own.

[hwillson]

It doesn’t sound like there is an outstanding issue here, so closing. Thanks!