@client directive breaks fragments

Intended outcome: Trying to use a fragment in a query with @client directive

export const GET_APPS = gql`
  fragment AppFragment on App {
    id
    name
  }
  query GetApps {
    apps @client {
      ...AppFragment
      # id
      # name
    }
  }
`

Returns the apps with their id and name fields(it works if i uncomment the two fields)

Actual outcome: The apps are returned with no fields at all

How to reproduce the issue: I’m just using a TypePolicies Query that returns an array of object with the id and name fields

Versions "@apollo/client": "^3.0.0-beta.43"

[hwillson]

@Banou26 thanks for updating your reproduction. This isn’t a bug though. You aren’t providing enough information in your read function to resolve the fragment properly. Your fragment is on the type Foo, but you aren’t referencing Foo when you return data from the foo read function. Update your code with the following, and it will work:

cache.policies.addTypePolicies({
  Query: {
    fields: {
      foo: {
        read: () => ({ bar: 'bar', __typename: "Foo" })
      }
    }
  }
});

[Banou26]

Still an issue under ^3.3.16 which is current latest

Repro here with the code example i gave: https://github.com/Banou26/apollo-client-bug-6175