Update the specs for re-relaying #1
Conversation
…ion/mutation/objectidentification spec
| mutation fields in a standardized way. These mutations accept and emit a | ||
| identifier string, which allows Relay to track mutations and responses. | ||
| identifier string, which allows Relay Classic to track mutations and responses. | ||
|
|
||
| All mutations may include in their input a `clientMutationId` string, which is | ||
| then returned as part of the object returned by the mutation field. |
There was a problem hiding this comment.
This doc could probably stay in relay? it's only for relay classic now
| way. | ||
|
|
||
| In the query, the connection model provides a standard mechanism for slicing | ||
| and paginating the result set. |
There was a problem hiding this comment.
I have a hard time understanding this sentence. I know you didn’t write this, but do you understand what it’s trying to convey?
There was a problem hiding this comment.
I think it's talking about always using the same args in each connection for pagination
There was a problem hiding this comment.
e.g. before after next the_other_one
There was a problem hiding this comment.
After reading further, I think they mean in the literal query text, and then what you said yeah
Co-Authored-By: orta <[email protected]>
Co-Authored-By: orta <[email protected]>
Co-Authored-By: orta <[email protected]>
| mutation fields in a standardized way. These mutations accept and emit a | ||
| identifier string, which allows Relay to track mutations and responses. | ||
| identifier string, which allows Relay Classic to track mutations and responses. |
There was a problem hiding this comment.
While this was a stated intent for Modern, the identifier string (clientMutationId) hasn't actually been removed yet. Nonetheless I'd leave this change in the upstream PR and then discuss it.
| object identifiers in a standardized way. In the query, the schema should | ||
| provide a standard mechanism for asking for an object by ID. In the response, | ||
| the schema provides a standard way of providing these IDs. | ||
| To provide options for GraphQL clients to elegantly handle for caching and data |
There was a problem hiding this comment.
Is “to handle for” English?
I like adding the examples 👍
Co-Authored-By: orta <[email protected]>
No description provided.