diff --git a/draft/index.html b/draft/index.html index 9d642628e..2b1c1469d 100644 --- a/draft/index.html +++ b/draft/index.html @@ -1473,7 +1473,7 @@
Type system extensions are used to represent a GraphQL type system which has been extended from some original type system. For example, this might be used by a local service to represent data a GraphQL client only accesses locally, or by a GraphQL service which is itself an extension of another GraphQL service.
+Type system extensions are used to represent a GraphQL type system which has been extended from some previous type system. For example, this might be used by a local service to represent data a GraphQL client only accesses locally, or by a GraphQL service which is itself an extension of another GraphQL service.
Tools which only seek to produce and extend schema and not execute requests may choose to only allow TypeSystemExtensionDocument and not allow ExecutableDefinition but should provide a descriptive error if present.
Schema extensions are used to represent a schema which has been extended from an original schema. For example, this might be used by a GraphQL service which adds additional operation types, or additional directives to an existing schema.
+Schema extensions are used to represent a schema which has been extended from a previous schema. For example, this might be used by a GraphQL service which adds additional operation types, or additional directives to an existing schema.
Type extensions are used to represent a GraphQL type which has been extended from some original type. For example, this might be used by a local service to represent additional fields a GraphQL client only accesses locally.
+Type extensions are used to represent a GraphQL type which has been extended from some previous type. For example, this might be used by a local service to represent additional fields a GraphQL client only accesses locally.
Scalar type extensions are used to represent a scalar type which has been extended from some original scalar type. For example, this might be used by a GraphQL tool or service which adds directives to an existing scalar.
+Scalar type extensions are used to represent a scalar type which has been extended from some previous scalar type. For example, this might be used by a GraphQL tool or service which adds directives to an existing scalar.
Scalar type extensions have the potential to be invalid if incorrectly defined.
Object type extensions are used to represent a type which has been extended from some original type. For example, this might be used to represent local data, or by a GraphQL service which is itself an extension of another GraphQL service.
+Object type extensions are used to represent a type which has been extended from some previous type. For example, this might be used to represent local data, or by a GraphQL service which is itself an extension of another GraphQL service.
In this example, a local data field is added to a Story
type:
Example № 63extend type Story {
isHiddenLocally: Boolean
@@ -2127,9 +2127,9 @@ The named type must already be defined and must be an Object type.
The fields of an Object type extension must have unique names; no two fields may share the same name.
-Any fields of an Object type extension must not be already defined on the original Object type.
-Any non-repeatable directives provided must not already apply to the original Object type.
-Any interfaces provided must not be already implemented by the original Object type.
+Any fields of an Object type extension must not be already defined on the previous Object type.
+Any non-repeatable directives provided must not already apply to the previous Object type.
+Any interfaces provided must not be already implemented by the previous Object type.
The resulting extended object type must be a super-set of all interfaces it implements.
@@ -2280,7 +2280,7 @@ extendinterfaceNameImplementsInterfacesoptDirectivesConst{
-Interface type extensions are used to represent an interface which has been extended from some original interface. For example, this might be used to represent common local data on many types, or by a GraphQL service which is itself an extension of another GraphQL service.
+Interface type extensions are used to represent an interface which has been extended from some previous interface. For example, this might be used to represent common local data on many types, or by a GraphQL service which is itself an extension of another GraphQL service.
In this example, an extended data field is added to a NamedEntity
type along with the types which implement it:
Example № 73extend interface NamedEntity {
nickname: String
@@ -2304,9 +2304,9 @@ The named type must already be defined and must be an Interface type.
The fields of an Interface type extension must have unique names; no two fields may share the same name.
-Any fields of an Interface type extension must not be already defined on the original Interface type.
-Any Object or Interface type which implemented the original Interface type must also be a super-set of the fields of the Interface type extension (which may be due to Object type extension).
-Any non-repeatable directives provided must not already apply to the original Interface type.
+Any fields of an Interface type extension must not be already defined on the previous Interface type.
+Any Object or Interface type which implemented the previous Interface type must also be a super-set of the fields of the Interface type extension (which may be due to Object type extension).
+Any non-repeatable directives provided must not already apply to the previous Interface type.
The resulting extended Interface type must be a super-set of all Interfaces it implements.
@@ -2387,7 +2387,7 @@ UnionTypeExtension
-
Union type extensions are used to represent a union type which has been extended from some original union type. For example, this might be used to represent additional local data, or by a GraphQL service which is itself an extension of another GraphQL service.
+Union type extensions are used to represent a union type which has been extended from some previous union type. For example, this might be used to represent additional local data, or by a GraphQL service which is itself an extension of another GraphQL service.
Type Validation
Union type extensions have the potential to be invalid if incorrectly defined.
@@ -2395,8 +2395,8 @@ The named type must already be defined and must be a Union type.
The member types of a Union type extension must all be Object base types; Scalar, Interface and Union types must not be member types of a Union. Similarly, wrapping types must not be member types of a Union.
All member types of a Union type extension must be unique.
-All member types of a Union type extension must not already be a member of the original Union type.
-Any non-repeatable directives provided must not already apply to the original Union type.
+All member types of a Union type extension must not already be a member of the previous Union type.
+Any non-repeatable directives provided must not already apply to the previous Union type.
@@ -2445,15 +2445,15 @@ EnumTypeExtension
-
Enum type extensions are used to represent an enum type which has been extended from some original enum type. For example, this might be used to represent additional local data, or by a GraphQL service which is itself an extension of another GraphQL service.
+Enum type extensions are used to represent an enum type which has been extended from some previous enum type. For example, this might be used to represent additional local data, or by a GraphQL service which is itself an extension of another GraphQL service.
Type Validation
Enum type extensions have the potential to be invalid if incorrectly defined.
- The named type must already be defined and must be an Enum type.
- All values of an Enum type extension must be unique.
-- All values of an Enum type extension must not already be a value of the original Enum.
-- Any non-repeatable directives provided must not already apply to the original Enum type.
+- All values of an Enum type extension must not already be a value of the previous Enum.
+- Any non-repeatable directives provided must not already apply to the previous Enum type.
@@ -2647,15 +2647,15 @@ InputObjectTypeExtension
-
Input object type extensions are used to represent an input object type which has been extended from some original input object type. For example, this might be used by a GraphQL service which is itself an extension of another GraphQL service.
+Input object type extensions are used to represent an input object type which has been extended from some previous input object type. For example, this might be used by a GraphQL service which is itself an extension of another GraphQL service.
Type Validation
Input object type extensions have the potential to be invalid if incorrectly defined.
- The named type must already be defined and must be a Input Object type.
- All fields of an Input Object type extension must have unique names.
-- All fields of an Input Object type extension must not already be a field of the original Input Object.
-- Any non-repeatable directives provided must not already apply to the original Input Object type.
+- All fields of an Input Object type extension must not already be a field of the previous Input Object.
+- Any non-repeatable directives provided must not already apply to the previous Input Object type.
diff --git a/index.html b/index.html
index 4bf63655b..2f423a7ea 100644
--- a/index.html
+++ b/index.html
@@ -1 +1 @@
- GraphQL Specification Versions GraphQL
Prerelease Working Draft Fri, Dec 6, 2024 Latest Release October 2021 Tue, Oct 26, 2021 Release Notes June 2018 Sun, Jun 10, 2018 Release Notes October 2016 Mon, Oct 31, 2016 Release Notes April 2016 Thu, Apr 7, 2016 Release Notes October 2015 Thu, Oct 1, 2015 Release Notes July 2015 Thu, Jul 2, 2015 Release Notes
+ GraphQL Specification Versions GraphQL
Prerelease Working Draft Thu, Dec 19, 2024 Latest Release October 2021 Tue, Oct 26, 2021 Release Notes June 2018 Sun, Jun 10, 2018 Release Notes October 2016 Mon, Oct 31, 2016 Release Notes April 2016 Thu, Apr 7, 2016 Release Notes October 2015 Thu, Oct 1, 2015 Release Notes July 2015 Thu, Jul 2, 2015 Release Notes