Turning off __typename consequences

Hey, there are a lot of issues about __typename added to data. There are use cases when you want to receive data exactly as it was asked. The advised solutions were to manually deeply remove __typename from data or to turn this off with addTypename: false.

What are the consequences of turning this off with addTypename: false, will it break cache somehow/make it slower/etc ?

[ikatun]

We dumped the react-apollo all together and switched to using our own library which exposes apollo through mobx. The library itself filters the extraneous __typename field.

Internally, it all just comes to this function

function removeTypename(data) {
  return typeof data === 'object' ? objectKeyFilter(data, ['__typename'], true) : data;
}

and then (for example in render function/method)

const cleanData = removeTypename(dataFromApollo);

objectKeyFilter being https://www.npmjs.com/package/object-key-filter

[ikatun]

If you want to avoid having to manually remove __typename from every response, you can just require this module https://www.npmjs.com/package/typename-monkey-patch somewhere near the entry point of your app. It monkey patches graphql HOC from react-apollo so that __typename is removed before sending data to your wrapped component.