时间戳

首页 > 解决方案 > 如何从导致突变失败的graphql响应中删除`__typename`字段

node.js - 如何从导致突变失败的graphql响应中删除`__typename`字段

问题描述

我尝试在 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 }),，由于突变中不需要的类型名，突变也会开始失败

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

标签： node.jsgraphqlapolloapollo-clientexpress-graphql

解决方案

从 GraphQL 响应中清除不需要的字段

在上面的帖子中，我已经发布了这个问题的答案，请参考它

推荐阅读