如何从失败的graphql响应中删除`__typename`字段

时间:2019-03-20 11:36:43

标签: node.js graphql apollo apollo-client express-graphql

我尝试在GraphQL的Apollo客户端中更改addTypeName:false

apollo.create({
  link: httpLinkWithErrorHandling,
  cache: new InMemoryCache({ addTypename: false }),
  defaultOptions: {
    watchQuery: {
      fetchPolicy: 'network-only',
      errorPolicy: 'all'
    }
  }

但是它可以工作,并且会在控制台中抛出以下消息

fragmentMatcher.js:26 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 Clientcan accurately match fragments.

Could not find __typename on Fragment  PopulatedOutageType

fragmentMatcher.js:28 DEPRECATION WARNING: using fragments without __typename is unsupported behavior and will be removed in future versions of Apollo client. You should fix this and set addTypename to true now.

即使我将false更改为true new InMemoryCache({ addTypename: true }),,由于突变中不需要的类型名,突变也开始失败

有什么办法可以解决这个问题

1 个答案:

答案 0 :(得分:0)

Cleaning Unwanted Fields From GraphQL Responses

在上面的主题中,我已经发布了此问题的答案,请参考