absinthe
absinthe
v1.7.5

View Source Absinthe.Phase behaviour (absinthe v1.7.5)

Behaviour for Absinthe Phases.

A phase takes an Absinthe.Blueprint document and returns another blueprint document. All validation, resolution, and result building happens via phases. See Absinthe.Pipeline for information on how to run phases. See the code under this namespace for information on individual phases.

Link to this section Summary

Types

result_t()
t()

Callbacks

run(any, any)

Functions

any_invalid?(nodes)
put_error(node, error)

Link to this section Types

Link to this type

result_t()

View Source 
@type result_t() ::
  {:ok, any()}
  | {:jump, any(), t()}
  | {:insert, any(), t() | [t()]}
  | {:replace, any(), t() | [t()]}
  | {:error, any()}
  | {:record_phases, any(), (any(), any() -> any())}
Link to this type

t()

View Source 
@type t() :: module()

Link to this section Callbacks

Link to this callback

run(any, any)

View Source 
@callback run(any(), any()) :: result_t()

Link to this section Functions

Link to this function

any_invalid?(nodes)

View Source
Link to this function

put_error(node, error)

View Source 
@spec put_error(Absinthe.Blueprint.node_t(), Absinthe.Phase.Error.t()) ::
  Absinthe.Blueprint.node_t()