具有动态键的对象的Apollo/GraphQL字段类型

本文是小编为大家收集整理的关于具有动态键的对象的Apollo/GraphQL字段类型的处理/解决方法，可以参考本文帮助大家快速定位并解决问题，中文翻译不准确的可切换到English标签页查看源文。

中文
English

问题描述

假设我的GraphQl Server想要获取以下数据为JSON，其中person3和person5是某些ID:

"persons": {
  "person3": {
    "id": "person3",
    "name": "Mike"
  },
  "person5": {
    "id": "person5",
    "name": "Lisa"
  }
}

问题:如何使用Apollo创建模式类型定义?

键person3和person5此处是根据我的查询(即查询中使用的area)动态生成的.因此，在另一个时间，我可能会得到person1，person2，person3返回. 如您所见，persons不是一个可觉得的，因此以下内容无法用Apollo进行的GraphQl类型定义来工作:

type Person {
  id: String
  name: String
}
type Query {
  persons(area: String): [Person]
}

persons对象中的键可能总是不同的.

当然，一种解决方案是将传入的JSON数据转换为使用persons的数组，但是是否可以这样处理数据?

其他推荐答案

您可以编写自己的GraphQLScalarType，并精确地描述您的对象和动态键，允许的内容以及不允许或不允许的东西.

参见/a>

您可以看看 taion/graphql-type-json 创建允许和转换任何类型内容的标量:

https://github.com/taion/graphql-type-json/blob/master/src/index.js

其他推荐答案

我在模式中有动态键的类似问题，最终使用这样的解决方案:

query lookupPersons {
  persons {
    personKeys
    person3: personValue(key: "person3") {
      id
      name
    }
  }
}

{
  data: {
    persons: {
      personKeys: ["person1", "person2", "person3"]
      person3: {
        id: "person3"
        name: "Mike"
      }
    }
  }
}

通过将复杂性转移到查询中，它简化了响应形状. 与JSON方法相比的优势是，它不需要客户端的任何必要性

venryx的其他信息:可能适合我查询的模式看起来像这样:

type Person {
  id: String
  name: String
}

type PersonsResult {
  personKeys: [String]
  personValue(key: String): Person
}

type Query {
  persons(area: String): PersonsResult
}

顺便说一句，如果您的数据集变得足够大，您可能还要在personKeys上进行分页，此时，您应该研究 https://relay.dev/graphql/connections.htm

本文地址：https://www.itbaoku.cn/post/1938022.html

百度翻译此文有道翻译此文

问题描述

Let's say my graphql server wants to fetch the following data as JSON where person3 and person5 are some id's:

"persons": {
  "person3": {
    "id": "person3",
    "name": "Mike"
  },
  "person5": {
    "id": "person5",
    "name": "Lisa"
  }
}

Question: How to create the schema type definition with apollo?

The keys person3 and person5 here are dynamically generated depending on my query (i.e. the area used in the query). So at another time I might get person1, person2, person3 returned. As you see persons is not an Iterable, so the following won't work as a graphql type definition I did with apollo:

type Person {
  id: String
  name: String
}
type Query {
  persons(area: String): [Person]
}

The keys in the persons object may always be different.

One solution of course would be to transform the incoming JSON data to use an array for persons, but is there no way to work with the data as such?

其他推荐答案

You can write your own GraphQLScalarType and precisely describe your object and your dynamic keys, what you allow and what you do not allow or transform.

See https://graphql.org/graphql-js/type/#graphqlscalartype

You can have a look at taion/graphql-type-json where he creates a Scalar that allows and transforms any kind of content:

https://github.com/taion/graphql-type-json/blob/master/src/index.js

其他推荐答案

I had a similar problem with dynamic keys in a schema, and ended up going with a solution like this:

query lookupPersons {
  persons {
    personKeys
    person3: personValue(key: "person3") {
      id
      name
    }
  }
}

returns:

{
  data: {
    persons: {
      personKeys: ["person1", "person2", "person3"]
      person3: {
        id: "person3"
        name: "Mike"
      }
    }
  }
}

by shifting the complexity to the query, it simplifies the response shape. the advantage compared to the JSON approach is it doesn't need any deserialisation from the client

Additional info for Venryx: a possible schema to fit my query looks like this:

type Person {
  id: String
  name: String
}

type PersonsResult {
  personKeys: [String]
  personValue(key: String): Person
}

type Query {
  persons(area: String): PersonsResult
}

As an aside, if your data set for persons gets large enough, you're going to probably want pagination on personKeys as well, at which point, you should look into https://relay.dev/graphql/connections.htm

上一篇：如何使用Apollo客户端将两个GraphQL查询依次连接起来

下一篇：突变方法是否需要在顶层？