Skip to content

Commit 9b962f7

Browse files
committed
edits
1 parent d1a265b commit 9b962f7

File tree

4 files changed

+14
-11
lines changed

4 files changed

+14
-11
lines changed

articles/api-center/overview.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ author: dlepow
55

66
ms.service: api-center
77
ms.topic: overview
8-
ms.date: 03/01/2024
8+
ms.date: 05/02/2024
99
ms.author: danlep
1010
ms.custom: references_regions
1111
---

articles/api-management/configure-graphql-resolver.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ author: dlepow
66

77
ms.service: api-management
88
ms.topic: article
9-
ms.date: 04/24/2024
9+
ms.date: 05/02/2024
1010
ms.author: danlep
1111
---
1212

@@ -29,7 +29,7 @@ Currently, API Management supports resolvers that can access the following data
2929
* Each resolver resolves data for a single field. To resolve data for multiple fields, configure a separate resolver for each.
3030
* Resolver-scoped policies are evaluated *after* any `inbound` and `backend` policies in the policy execution pipeline. They don't inherit policies from other scopes. For more information, see [Policies in API Management](api-management-howto-policies.md).
3131
* You can configure API-scoped policies for a GraphQL API, independent of the resolver-scoped policies. For example, add a [validate-graphql-request](validate-graphql-request-policy.md) policy to the `inbound` scope to validate the request before the resolver is invoked. Configure API-scoped policies on the **API policies** tab for the API.
32-
* To use interface and union types in GraphQL resolvers, the backend response must either already contain the `__typename` field, or be altered using the set-body policy to include `__typename`.
32+
* To support interface and union types in GraphQL resolvers, the backend response must either already contain the `__typename` field, or be altered using the [set-body](set-body-policy.md) policy to include `__typename`.
3333

3434
## Prerequisites
3535

articles/api-management/graphql-apis-overview.md

Lines changed: 10 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -47,6 +47,7 @@ In API Management, add a GraphQL API from a GraphQL schema, either retrieved fro
4747

4848
* Data object types and fields that clients can request from a GraphQL API
4949
* Operation types allowed on the data, such as queries
50+
* Other types, such as unions and interfaces, that provide additional flexibility and control over the data
5051

5152
For example, a basic GraphQL schema for user data and a query for all users might look like:
5253

@@ -61,20 +62,23 @@ type User {
6162
}
6263
```
6364

64-
API Management supports the following operation types in GraphQL schemas. For more information about these operation types, see the [GraphQL specification](https://spec.graphql.org/October2021/#sec-Subscription-Operation-Definitions).
65+
### Operation types
66+
67+
API Management supports the following operation types in GraphQL schemas. For more information about these operation types, see the [GraphQL specification](https://spec.graphql.org/October2021/#sec-Root-Operation-Types).
6568

6669
* **Query** - Fetches data, similar to a `GET` operation in REST
6770
* **Mutation** - Modifies server-side data, similar to a `PUT` or `PATCH` operation in REST
6871
* **Subscription** - Enables notifying subscribed clients in real time about changes to data on the GraphQL service
6972

7073
For example, when data is modified via a GraphQL mutation, subscribed clients could be automatically notified about the change.
7174

72-
> [!IMPORTANT]
73-
> API Management supports subscriptions implemented using the [graphql-ws](https://github.com/enisdenjo/graphql-ws) WebSocket protocol. Queries and mutations aren't supported over WebSocket.
74-
>
75+
> [!IMPORTANT]
76+
> API Management supports subscriptions implemented using the [graphql-ws](https://github.com/enisdenjo/graphql-ws) WebSocket protocol. Queries and mutations aren't supported over WebSocket.
77+
>
78+
79+
### Other types
7580

76-
> [!NOTE]
77-
> API Management also supports the [union](https://spec.graphql.org/October2021/#sec-Unions) and [interface](https://spec.graphql.org/October2021/#sec-Interfaces) types in GraphQL schemas.
81+
API Management supports the [union](https://spec.graphql.org/October2021/#sec-Unions) and [interface](https://spec.graphql.org/October2021/#sec-Interfaces) types in GraphQL schemas.
7882

7983
## Resolvers
8084

articles/api-management/http-data-source-policy.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ author: dlepow
66

77
ms.service: api-management
88
ms.topic: article
9-
ms.date: 03/19/2024
9+
ms.date: 05/02/2024
1010
ms.author: danlep
1111
---
1212

@@ -97,7 +97,6 @@ The `http-data-source` resolver policy configures the HTTP request and optionall
9797

9898
* To configure and manage a resolver with this policy, see [Configure a GraphQL resolver](configure-graphql-resolver.md).
9999
* This policy is invoked only when resolving a single field in a matching GraphQL operation type in the schema.
100-
* This policy supports GraphQL [union types](https://spec.graphql.org/October2021/#sec-Unions).
101100

102101
## Examples
103102

0 commit comments

Comments
 (0)