Skip to content

Commit 37d5a2d

Browse files
committed
remove confusing attempt at clarification
1 parent 058a4c6 commit 37d5a2d

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

rfcs/ObjectIdentification.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ Also, the Global Object Identification pattern is not enough for the use case of
1616

1717
This proposal introduces a new introspection field `__id`, which can be queried on any object, interface or union type.
1818
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+
2020
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.
2121

2222
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

Comments
 (0)