Package

sangria.execution

batch

Permalink

package batch

Visibility
  1. Public
  2. All

Type Members

  1. case class BatchExecutionError(message: String, eh: Executor.ExceptionHandler) extends ExecutionError with QueryAnalysisError with Product with Serializable

    Permalink

  2. case class BatchExecutionPlan(exportOperations: Map[String, ExportOperation], dependencies: Map[String, Vector[(String, Set[String])]]) extends Product with Serializable

    Permalink

  3. case class BatchExecutionViolationError(violations: Vector[Violation], eh: Executor.ExceptionHandler) extends ExecutionError with QueryAnalysisError with WithViolations with Product with Serializable

    Permalink

  4. case class CircularOperationDependencyViolation(operationName: String, path: Vector[String], sourceMapper: Option[SourceMapper], locations: List[AstLocation]) extends AstNodeViolation with Product with Serializable

    Permalink

  5. case class UndefinedVariableDefinitionViolation(operationName: String, variableName: String, sourceMapper: Option[SourceMapper], locations: List[AstLocation]) extends AstNodeViolation with Product with Serializable

    Permalink

  6. case class VariableDefinitionInferenceViolation(operationName: String, variableName: String, type1: String, type2: String, sourceMapper: Option[SourceMapper], locations: List[AstLocation]) extends AstNodeViolation with Product with Serializable

    Permalink

Value Members

  1. object BatchExecutionPlan extends Serializable

    Permalink

  2. object BatchExecutor

    Permalink

    EXPERIMENTAL

    EXPERIMENTAL

    Batch query executor which provides following features:

    - Allows specifying multiple operationNames when executing a GraphQL query document. All operations would be executed in order inferred from the dependencies between queries. - Support for @export(as: "foo") directive. This directive allows you to save the results of the query execution and then use it as a variable in a different query within the same document. This provides a way to define data dependencies between queries. - When used with @export directive, the variables would be automatically inferred by the execution engine, so you don't need to declare them explicitly (though you can)

Ungrouped