View Source argo_graphql_language_input_object_type_definition (argo v1.0.4)

Summary

Functions

Schema extensions without additional operation type definitions must not be followed by a { (such as a query shorthand) to avoid parsing ambiguity. The same limitation applies to the type definitions and extensions below.

Types

-type context() ::
    #{name := argo_types:name(),
      description => unicode:unicode_binary(),
      directives => argo_graphql_language_directives_const:t(),
      fields => argo_graphql_language_input_fields_definition:t()}.
-type t() ::
    #argo_graphql_language_input_object_type_definition{location :: erl_anno:location(),
                                                        name :: argo_types:name(),
                                                        description ::
                                                            none |
                                                            {some, unicode:unicode_binary()},
                                                        directives ::
                                                            none |
                                                            {some,
                                                             argo_graphql_language_directives_const:t()},
                                                        fields ::
                                                            none |
                                                            {some,
                                                             argo_graphql_language_input_fields_definition:t()}}.

Functions

Link to this function

format(Formatter1, Type)

View Source
-spec format(Formatter1, Type :: t()) -> Formatter2
          when Formatter1 :: argo_graphql_formatter:t(), Formatter2 :: argo_graphql_formatter:t().
Link to this function

is_ambiguous(Definition)

View Source
-spec is_ambiguous(Definition) -> boolean() when Definition :: t().
Schema extensions without additional operation type definitions must not be followed by a { (such as a query shorthand) to avoid parsing ambiguity. The same limitation applies to the type definitions and extensions below.
Link to this function

parse(Context, Location)

View Source
-spec parse(Context, Location) -> InputObjectTypeDefinition
         when
             Context :: context(),
             Location :: erl_anno:location(),
             InputObjectTypeDefinition :: t().