1.1.1Schema Extension

SetSchemaDefinition and SetSchemaExtension are grammatically identical to the Schema in the GraphQL Specification.

1.2.1Type Extensions

1.3.1Scalar Extensions

1.4.1Object Extensions

1.5.1Field Extensions

It is possible for the type definition of a field to only be present in that field’s extension. Likewise, we need to be able to extend a field (like deprecating it) with a guarantee that the field’s type will not change through the extension.

Field extensions are different from fields defined by a type extension. The below is valid syntax:

graphql field-extension extend type Person { extend age @deprecated name } type Business { extend name @deprecated } To become a valid GraphQL Spec document, the above would need to be union‘d with a document like:

graphql field-extension-merge type Person { age: Int extend name: String @deprecated } extend type Business { name: String }

resulting in:

graphql field-extension-union type Person { age: Int @deprecated name: String @deprecated } type Business { name: String @deprecated } which is now a valid GraphQL Type System Document.

The syntax of allowing field definitions without a type definition enables tooling, such as diff tools, to have a valid syntax for how a schema is evolving, even if the semantic meaning of the syntax would not produce a valid GraphQL Schema.

1.5.2Field Arguments

1.5.3Input Values

1.5.4Input Value Extensions

Similar to Field Definitions and Extensions, Input Value Definitions and Extensions cannot may elide the input value’s type.

1.6.1Union Extensions

SetUntionTypeExtension is gramatically identical to the Unions in the GraphQL Specification.

1.7.1Enum Values

1.7.2Enum Extensions

1.10.1Directive Extensions