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
59
+
/// by using persisted queries.
60
+
///
61
+
/// - parameter queryStrategy: The field execution strategy to use for query requests
62
+
/// - parameter mutationStrategy: The field execution strategy to use for mutation requests
63
+
/// - parameter subscriptionStrategy: The field execution strategy to use for subscription requests
64
+
/// - parameter instrumentation: The instrumentation implementation to call during the parsing, validating, execution, and field resolution stages.
65
+
/// - parameter queryRetrieval: The PersistedQueryRetrieval instance to use for looking up queries
66
+
/// - parameter queryId: The id of the query to execute
67
+
/// - parameter rootValue: The value provided as the first argument to resolver functions on the top level type (e.g. the query object type).
68
+
/// - parameter contextValue: A context value provided to all resolver functions functions
69
+
/// - parameter variableValues: A mapping of variable name to runtime value to use for all variables defined in the `request`.
70
+
/// - parameter operationName: The name of the operation to use if `request` contains multiple possible operations. Can be omitted if `request` contains only one operation.
71
+
///
72
+
/// - throws: throws GraphQLError if an error occurs while parsing the `request`.
73
+
///
74
+
/// - 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.
0 commit comments