Structure Design at the API Level
The schema definitions are on the server side. What you see at the application side is being exposed as a result of the schema design.
The GraphQL list modifier is an easy way to generate a sub-branch of the result tree. In our Email example, we have plenty of lists. For example, the keywords tagging a message:
keywords: [Keyword] @relation(name: "Tags")
Lists can handle nulls, which are syntactically visualized in GraphQL:
The data can be null: [Keyword]
The data cannot be null: [Keyword!]
The list cannot be null: [Keyword!]!
Another GraphQL construct ...
