Interface Operation<Data, Variables>

The inputs to urql's Exchange pipeline to instruct them to execute a GraphQL operation.

Remarks

An Operation, in urql, starts a GraphQLRequest and are events. The kind of an Operation can be set to any operation kind of GraphQL, namely query, mutation, or subscription. To terminate an operation, once it's cancelled, a teardown kind event is sent.

The ExchangeIO type describes how Exchanges receive Operations and return OperationResults, using teardown Operations to cancel ongoing operations.

See

https://urql.dev/goto/docs/architecture/#the-client-and-exchanges for more information on the flow of Exchanges.

Type Parameters

Hierarchy

Properties

Holds additional metadata for an Operation used to execute it.

Remarks

The OperationContext is created by the Client but may also be modified by Exchanges and is used as metadata by them.

extensions?: RequestExtensions

Additional metadata that a GraphQL API may accept for spec extensions.

See

https://github.com/graphql/graphql-over-http/blob/1928447/spec/GraphQLOverHTTP.md#request-parameters for the GraphQL over HTTP spec

key: number

Unique identifier for the GraphQLRequest.

Remarks

This is a key that combines the unique key of the query and the variables into a unique key for the GraphQLRequest. Any request with the same query and variables will have a unique key by which results and requests can be identified as identical.

Internally, a stable, cached key is generated for the DocumentNode and for the variables and both will be combined into a combined key which is set here, based on a DJB2 hash,

The variables will change the key even if they contain a non-JSON reference. If you pass a custom class instance to variables that doesn't contain a toString or toJSON method, a stable but random identifier will replace this class to generate a key.

The OperationType describing the kind of Operation.

Remarks

This is used to describe what to do with the GraphQLRequest of an Operation and is set to a GraphQL operation type (query, mutation, or subscription) to start an Operation; and to teardown to cancel an operation, which either terminates it early or lets exchanges know that no consumer is interested in this operation any longer.

query: DocumentNode | TypedDocumentNode<Data, Variables>

A GraphQL document to execute against a cache or API.

Remarks

A GraphQLRequest is executed against an operation in a GraphQL document. In urql, we expect a document to only contain a single operation that is executed rather than multiple ones by convention.

variables: Variables

Variables used to execute the query document.

Remarks

The variables, based either on the AnyVariables type or the TypedDocumentNode's provided generic, are sent to the GraphQL API to execute a request.

Generated using TypeDoc