You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/source/errors.md
+18
Original file line number
Diff line number
Diff line change
@@ -89,6 +89,24 @@ The following errors might be raised during composition:
89
89
|`ROOT_SUBSCRIPTION_USED`| A subgraph's schema defines a type with the name `subscription`, while also specifying a _different_ type name as the root query object. This is not allowed. | 0.x ||
90
90
|`SATISFIABILITY_ERROR`| Subgraphs can be merged, but the resulting supergraph API would have queries that cannot be satisfied by those subgraphs. | 2.0.0 ||
91
91
|`SHAREABLE_HAS_MISMATCHED_RUNTIME_TYPES`| A shareable field return type has mismatched possible runtime types in the subgraphs in which the field is declared. As shared fields must resolve the same way in all subgraphs, this is almost surely a mistake. | 2.0.0 ||
92
+
|`SOURCE_API_HTTP_BASE_URL_INVALID`| The `@sourceAPI` directive must specify a valid http.baseURL | 2.7.0 ||
93
+
|`SOURCE_API_NAME_INVALID`| Each `@sourceAPI` directive must take a unique and valid name as an argument | 2.7.0 ||
94
+
|`SOURCE_API_PROTOCOL_INVALID`| Each `@sourceAPI` directive must specify exactly one of the known protocols | 2.7.0 ||
95
+
|`SOURCE_FIELD_API_ERROR`| The `api` argument of the `@sourceField` directive must match a valid `@sourceAPI` name | 2.7.0 ||
96
+
|`SOURCE_FIELD_HTTP_BODY_INVALID`| If `@sourceField` specifies http.body, it must be a valid `JSONSelection` matching available arguments and fields | 2.7.0 ||
97
+
|`SOURCE_FIELD_HTTP_METHOD_INVALID`| The `@sourceField` directive must specify at most one of `http.{GET,POST,PUT,PATCH,DELETE}`| 2.7.0 ||
98
+
|`SOURCE_FIELD_HTTP_PATH_INVALID`| The `@sourceField` directive must specify a valid URL template for `http.{GET,POST,PUT,PATCH,DELETE}`| 2.7.0 ||
99
+
|`SOURCE_FIELD_NOT_ON_ROOT_OR_ENTITY_FIELD`| The `@sourceField` directive must be applied to a field of the `Query` or `Mutation` types, or of an entity type | 2.7.0 ||
100
+
|`SOURCE_FIELD_PROTOCOL_INVALID`| If `@sourceField` specifies a protocol, it must match the corresponding `@sourceAPI` protocol | 2.7.0 ||
101
+
|`SOURCE_FIELD_SELECTION_INVALID`| The `selection` argument of the `@sourceField` directive must be a valid `JSONSelection` that outputs fields of the GraphQL type | 2.7.0 ||
102
+
|`SOURCE_HTTP_HEADERS_INVALID`| The `http.headers` argument of `@source*` directives must specify valid HTTP headers | 2.7.0 ||
103
+
|`SOURCE_TYPE_API_ERROR`| The `api` argument of the `@sourceType` directive must match a valid `@sourceAPI` name | 2.7.0 ||
104
+
|`SOURCE_TYPE_HTTP_BODY_INVALID`| If the `@sourceType` specifies `http.body`, it must be a valid `JSONSelection`| 2.7.0 ||
105
+
|`SOURCE_TYPE_HTTP_METHOD_INVALID`| The `@sourceType` directive must specify exactly one of `http.GET` or `http.POST`| 2.7.0 ||
106
+
|`SOURCE_TYPE_HTTP_PATH_INVALID`| The `@sourceType` directive must specify a valid URL template for `http.GET` or `http.POST`| 2.7.0 ||
107
+
|`SOURCE_TYPE_ON_NON_OBJECT_OR_NON_ENTITY`| The `@sourceType` directive must be applied to an object or interface type that also has `@key`| 2.7.0 ||
108
+
|`SOURCE_TYPE_PROTOCOL_INVALID`| The `@sourceType` directive must specify the same protocol as its corresponding `@sourceAPI`| 2.7.0 ||
109
+
|`SOURCE_TYPE_SELECTION_INVALID`| The `selection` argument of the `@sourceType` directive must be a valid `JSONSelection` that outputs fields of the GraphQL type | 2.0.0 ||
92
110
|`TYPE_DEFINITION_INVALID`| A built-in or federation type has an invalid definition in the schema. | 2.0.0 ||
93
111
|`TYPE_KIND_MISMATCH`| A type has the same name in different subgraphs, but a different kind. For instance, one definition is an object type but another is an interface. | 2.0.0 | Replaces: `VALUE_TYPE_KIND_MISMATCH`, `EXTENSION_OF_WRONG_KIND`, `ENUM_MISMATCH_TYPE`|
94
112
|`TYPE_WITH_ONLY_UNUSED_EXTERNAL`| A federation 1 schema has a composite type comprised only of unused external fields. Note that this error can _only_ be raised for federation 1 schema as federation 2 schema do not allow unused external fields (and errors with code EXTERNAL_UNUSED will be raised in that case). But when federation 1 schema are automatically migrated to federation 2 ones, unused external fields are automatically removed, and in rare case this can leave a type empty. If that happens, an error with this code will be raised | 2.0.0 ||
0 commit comments