Input Object Type Definition¶
The GraphQL specification defines Input Object Type for complex inputs. It is similar to ObjectType except that it's fields have no args or resolve options and their type must be input type.
Writing Input Object Types¶
In graphql-php Input Object Type is an instance of GraphQL\Type\Definition\InputObjectType
(or one of its subclasses) which accepts configuration array in its constructor:
use GraphQL\Type\Definition\Type;
use GraphQL\Type\Definition\InputObjectType;
$filters = new InputObjectType([
'name' => 'StoryFiltersInput',
'fields' => [
'author' => [
'type' => Type::id(),
'description' => 'Only show stories with this author id'
],
'popular' => [
'type' => Type::boolean(),
'description' => 'Only show popular stories (liked by several people)'
],
'tags' => [
'type' => Type::listOf(Type::string()),
'description' => 'Only show stories which contain all of those tags'
]
]
]);
Every field may be of other InputObjectType (thus complex hierarchies of inputs are possible)
Configuration options¶
The constructor of InputObjectType
accepts an array
with the following options:
Option | Type | Notes |
---|---|---|
name | string |
Required. Unique name of this object type within Schema |
fields | array or callable |
Required. An array describing object fields or callable returning such an array (see below). |
description | string |
Plain-text description of this type for clients (e.g. used by GraphiQL for auto-generated documentation) |
parseValue | callable(array<string, mixed>): mixed |
Converts incoming values from their array representation to something else (e.g. a value object) |
Every field is an array with following entries:
Option | Type | Notes |
---|---|---|
name | string |
Required. Name of the input field. When not set - inferred from fields array key |
type | Type |
Required. Instance of one of Input Types (Scalar, Enum, InputObjectType + any combination of those with nonNull and listOf modifiers) |
description | string |
Plain-text description of this input field for clients (e.g. used by GraphiQL for auto-generated documentation) |
defaultValue | scalar |
Default value of this input field. Use the internal value if specifying a default for an enum type |
Using Input Object Type¶
In the example above we defined our InputObjectType. Now let's use it in one of field arguments:
use GraphQL\Type\Definition\Type;
use GraphQL\Type\Definition\ObjectType;
$queryType = new ObjectType([
'name' => 'Query',
'fields' => [
'stories' => [
'type' => Type::listOf($storyType),
'args' => [
'filters' => [
'type' => $filters,
'defaultValue' => [
'popular' => true
]
]
],
'resolve' => fn ($rootValue, array $args): array => DataSource::filterStories($args['filters']),
]
]
]);
(note that you can define defaultValue for fields with complex inputs as associative array).
Then GraphQL query could include filters as literal value:
{
stories(filters: { author: "1", popular: false })
}
Or as query variable:
query ($filters: StoryFiltersInput!) {
stories(filters: $filters)
}
$variables = [
'filters' => [
"author" => "1",
"popular" => false
]
];
graphql-php will validate the input against your InputObjectType definition and pass it to your
resolver as $args['filters']
Converting input object array to value object¶
If you want more type safety you can choose to parse the input array into a value object.
use GraphQL\Type\Definition\Type;
use GraphQL\Type\Definition\InputObjectType;
final class StoryFiltersInput
{
public string $author;
public ?bool $popular;
public array $tags;
public function __construct(string $author, ?bool $popular, array $tags)
{
$this->author = $author;
$this->popular = $popular;
$this->tag = $tag;
}
}
$filters = new InputObjectType([
'name' => 'StoryFiltersInput',
'fields' => [
'author' => [
'type' => Type::nonNull(Type::string()),
],
'popular' => [
'type' => Type::boolean(),
],
'tags' => [
'type' => Type::nonNull(Type::listOf(Type::string())),
]
],
'parseValue' => fn(array $values) => new StoryFiltersInput(
$values['author'],
$values['popular'] ?? null,
$values['tags']
),
]);
The value of $args['filters']
will now be an instance of StoryFiltersInput
.
The incoming values are converted using a depth-first traversal. Thus, nested input values
will be passed through their respective parseValue
functions before the parent receives their value.