Skip to content

Commit be6938c

Browse files
committed
revert back to MemberCoordinates
1 parent 7b75489 commit be6938c

File tree

1 file changed

+10
-3
lines changed

1 file changed

+10
-3
lines changed

spec/Section 3 -- Type System.md

Lines changed: 10 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -2195,14 +2195,21 @@ _schema element_ within a GraphQL Schema.
21952195
:: A _schema element_ can be a named type, a field, an input field, an enum
21962196
value, a field argument, a directive, or a directive argument.
21972197

2198+
:: The _containing element_ of a _schema element_ is the schema element with one
2199+
fewer {Name} token that syntactically contains it. Specifically:
2200+
2201+
- {MemberCoordinate} has a {TypeCoordinate} containing element.
2202+
- {ArgumentCoordinate} has a {MemberCoordinate} containing element.
2203+
- {DirectiveArgumentCoordinate} has a {DirectiveCoordinate} containing element.
2204+
- {TypeCoordinate} and {DirectiveCoordinate} have no containing element.
2205+
21982206
A _schema coordinate_ is always unique. Each _schema element_ can be referenced
21992207
by exactly one possible schema coordinate.
22002208

22012209
A _schema coordinate_ may refer to either a defined or built-in _schema
22022210
element_. For example, `String` and `@deprecated(reason:)` are both valid schema
2203-
coordinates which refer to built-in schema elements. However it must not refer
2204-
to a meta-field. For example, `Business.__typename` is _not_ a valid schema
2205-
coordinate.
2211+
coordinates which refer to built-in schema elements. Meta-fields may also be
2212+
referenced. For example, `Business.__typename` is a valid schema coordinate.
22062213

22072214
Note: Union members are not valid _schema coordinate_ as they reference existing
22082215
types in the schema. This preserves the uniqueness property of a _schema

0 commit comments

Comments
 (0)