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
/// This is the primary entry point function for fulfilling GraphQL operations
236
+
/// by parsing, validating, and executing a GraphQL document along side a
237
+
/// GraphQL schema.
238
+
///
239
+
/// More sophisticated GraphQL servers, such as those which persist queries,
240
+
/// may wish to separate the validation and execution phases to a static time
241
+
/// tooling step, and a server runtime step.
242
+
///
243
+
/// - parameter queryStrategy: The field execution strategy to use for query requests
244
+
/// - parameter mutationStrategy: The field execution strategy to use for mutation requests
245
+
/// - parameter subscriptionStrategy: The field execution strategy to use for subscription requests
246
+
/// - parameter instrumentation: The instrumentation implementation to call during the parsing, validating, execution, and field resolution stages.
247
+
/// - parameter schema: The GraphQL type system to use when validating and executing a query.
248
+
/// - parameter request: A GraphQL language formatted string representing the requested operation.
249
+
/// - parameter rootValue: The value provided as the first argument to resolver functions on the top level type (e.g. the query object type).
250
+
/// - parameter contextValue: A context value provided to all resolver functions functions
251
+
/// - parameter variableValues: A mapping of variable name to runtime value to use for all variables defined in the `request`.
252
+
/// - parameter operationName: The name of the operation to use if `request` contains multiple possible operations. Can be omitted if `request` contains only one operation.
253
+
///
254
+
/// - throws: throws GraphQLError if an error occurs while parsing the `request`.
255
+
///
256
+
/// - returns: returns a `Map` dictionary containing the result of the query inside the key `data` and any validation or execution errors inside the key `errors`. The value of `data` might be `null` if, for example, the query is invalid. It's possible to have both `data` and `errors` if an error occurs only in a specific field. If that happens the value of that field will be `null` and there will be an error inside `errors` specifying the reason for the failure and the path of the failed field.
/// This is the primary entry point function for fulfilling GraphQL subscription
287
+
/// operations by parsing, validating, and executing a GraphQL subscription
288
+
/// document along side a GraphQL schema.
289
+
///
290
+
/// More sophisticated GraphQL servers, such as those which persist queries,
291
+
/// may wish to separate the validation and execution phases to a static time
292
+
/// tooling step, and a server runtime step.
293
+
///
294
+
/// - parameter queryStrategy: The field execution strategy to use for query requests
295
+
/// - parameter mutationStrategy: The field execution strategy to use for mutation requests
296
+
/// - parameter subscriptionStrategy: The field execution strategy to use for subscription requests
297
+
/// - parameter instrumentation: The instrumentation implementation to call during the parsing, validating, execution, and field resolution stages.
298
+
/// - parameter schema: The GraphQL type system to use when validating and executing a query.
299
+
/// - parameter request: A GraphQL language formatted string representing the requested operation.
300
+
/// - parameter rootValue: The value provided as the first argument to resolver functions on the top level type (e.g. the query object type).
301
+
/// - parameter contextValue: A context value provided to all resolver functions
302
+
/// - parameter variableValues: A mapping of variable name to runtime value to use for all variables defined in the `request`.
303
+
/// - parameter operationName: The name of the operation to use if `request` contains multiple possible operations. Can be omitted if `request` contains only one operation.
304
+
///
305
+
/// - throws: throws GraphQLError if an error occurs while parsing the `request`.
306
+
///
307
+
/// - returns: returns a SubscriptionResult containing the subscription observable inside the key `observable` and any validation or execution errors inside the key `errors`. The
308
+
/// value of `observable` might be `null` if, for example, the query is invalid. It's not possible to have both `observable` and `errors`. The observable payloads are
309
+
/// GraphQLResults which contain the result of the query inside the key `data` and any validation or execution errors inside the key `errors`. The value of `data` might be `null`.
310
+
/// It's possible to have both `data` and `errors` if an error occurs only in a specific field. If that happens the value of that field will be `null` and there
311
+
/// will be an error inside `errors` specifying the reason for the failure and the path of the failed field.
0 commit comments