[Feature idea] Remove __typename requirement from writeFragment

[lorensr]

client.writeFragment({
  id: '5',
  fragment: gql`
    fragment myTodo on Todo {
      completed
      __typename
    }
  `,
  data: {
    completed: true,
    __typename: 'Todo'
  },
});

It would be nice if I didn't have to include __typename in the fragment and __typename: 'Todo' in the data. Could it default to not writing __typename, or using the existing __typename?

[Poincare]

I guess we could just addTypename the fragment to get rid of the first part of the issue. This sounds like a good idea to me. @jbaxleyiii , thoughts?

[alex996]

Furthermore, I don't understand how the docs suggest using writeFragment without __typename. Unless I include it, I end up with console warnings, whether I explicitly set addTypename in InMemoryCache to true or not (which it should be by default...):

You're using fragments in your queries, but either don't have the addTypename: true option set in Apollo Client, or you are trying to write a fragment to the store without the __typename. Please turn on the addTypename option and include __typename when writing fragments so that Apollo Client can accurately match fragments.

[hwillson]

To help provide a more clear separation between feature requests / discussions and bugs, and to help clean up the feature request / discussion backlog, Apollo Client feature requests / discussions are now being managed under the https://github.com/apollographql/apollo-feature-requests repository.

Migrated to: apollographql/apollo-feature-requests#21