@@ -2181,18 +2181,24 @@ SchemaCoordinate :
2181
2181
field , enum value , field argument , directive , or directive argument .
2182
2182
2183
2183
A *schema coordinate * is always unique . Each *schema element * may be referenced
2184
- by exactly one possible schema coordinate .
2184
+ by exactly one possible schema coordinate . There is a bidirectional 1:1 mapping .
2185
2185
2186
2186
A *schema coordinate * may refer to either a defined or built -in *schema element *.
2187
2187
For example , `String ` and `@deprecated (reason :)` are both valid schema
2188
2188
coordinates which refer to built -in schema elements . However it must not refer
2189
2189
to a meta -field . For example , `Business .__typename ` is *not * a valid
2190
2190
schema coordinate .
2191
2191
2192
+ Note : Unions members are not valid schema coordinates since they are references
2193
+ to existing types in the schema . This preserves the 1:1 mapping property of
2194
+ schema coordinates as stated above .
2195
+
2192
2196
Note : A {SchemaCoordinate } is not a definition within a GraphQL {Document }, but
2193
2197
a separate standalone grammar , intended to be used by tools to reference types ,
2194
- fields , and other *schema element *s . For example as references within
2195
- documentation , or as lookup keys in usage frequency tracking .
2198
+ fields , and other *schema element *s . Examples include : as references within
2199
+ documentation to refer to types and fields in a schema , a lookup key that can
2200
+ be used in logging tools to track how often particular fields are queried in
2201
+ production .
2196
2202
2197
2203
**Semantics **
2198
2204
0 commit comments