...
| Code Block |
|---|
query {
viewer {
organization {
members(first: 10) {
edges {
node {
name
avatar {
fileUrl
}
}
}
}
}
}
}
|
Example #2: Nesting
Querying with nested fields lets you replace multiple REST calls with fewer GraphQL queries. For example, retrieving a scenario along with its ar contents and associated groups using the REST API requires four separate calls:
...
| Code Block |
|---|
{
node(id: "ID_OF_SCENARIO")
... on Scenario
name
content {
fileUrl
fileContentType
fileUrlExpiresAt
}
groups {
nodes {
id
name
}
}
}
}
}
|
You can also extend the power of this query by substituting a variable for the pull request number.
...
| Code Block |
|---|
mutation {
updateScenario(id: "MDA6SXNzdWUyMjcyMDA2MTT", input:{name: 1234}) {
id
name
groups {
nodes {
id
name
}
}
}
}
|
Executing this query returns errors specifying the expected types for the operation:
| Code Block |
|---|
{
"data": null,
"errors": [
{
"message": "Argument 'input' on Field 'name' has an invalid value. Expected type 'String!'.",
"locations": [
{
"line": 3,
"column": 3
}
]
}
]
}
|