Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

3.10 Input Objects - clarify lists are permitted as Input fields #1068

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

3.10 Input Objects - clarify lists are permitted as Input fields #1068

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
f4fb1bd
3.10 Input Objects - clarify lists are permitted as Input fields
msolomon Dec 8, 2023
934e72e
Update spec/Section 3 -- Type System.md
msolomon Dec 8, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
5 changes: 3 additions & 2 deletions spec/Section 3 -- Type System.md
View file
Open in desktop
Expand Up @@ -1548,8 +1548,9 @@ Fields may accept arguments to configure their behavior. These inputs are often
scalars or enums, but they sometimes need to represent more complex values.

A GraphQL Input Object defines a set of input fields; the input fields are
either scalars, enums, or other input objects. This allows arguments to accept
arbitrarily complex structs.
scalars, enums, other input objects, or any wrapping type whose underlying base
type is one of those three. This allows arguments to accept arbitrarily complex
structs.

In this example, an Input Object called `Point2D` describes `x` and `y` inputs:

Expand Down