You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: rfcs/ObjectIdentification.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,7 +16,7 @@ Also, the Global Object Identification pattern is not enough for the use case of
16
16
17
17
This proposal introduces a new introspection field `__id`, which can be queried on any object, interface or union type.
18
18
The field is of type `ID` and for each individual type, the field must either always return a non-null value or always return null.
19
-
It might never be `null` for some objects of a type while being `ID!` for other objects of the same type.
19
+
20
20
If an `__id` field returns a non-null value for a type, this value must be guaranteed to uniquely identify the object when combined with the value of the `__typename` field.
21
21
22
22
This would allow clients without schema knowledge to query for `__id` on selection set and use the returned value for caching or referencing the object in other systems, if it is not `null`.
0 commit comments