Conversation
✅ Deploy Preview for graphql-spec-draft ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
Hi @robrichard , do you have any expected timeline for this feature? We are really excited to have this feature for our product! |
9ec7f65 to
f7e9124
Compare
|
The previous spec edits reached RFC2, should this also be RFC2? |
spec/Section 7 -- Response.md
Outdated
| "incremental": [ | ||
| { | ||
| "id": "1", | ||
| "data": { "lastName": "Skywalker" }] |
There was a problem hiding this comment.
| "data": { "lastName": "Skywalker" }] | |
| "data": { "lastName": "Skywalker" } |
|
|
||
| - If {serial} is not provided, initialize it to {false}. | ||
| - Let {groupedFieldSet} and {newDeferUsages} be the result of | ||
| {CollectFields(objectType, selectionSet, variableValues)}. |
There was a problem hiding this comment.
The new CollectFields requires a deferUsage argument ... this should be null for the initial call to CollectFields.
| {CollectFields(objectType, selectionSet, variableValues)}. | |
| {CollectFields(objectType, selectionSet, null, variableValues)}. |
Also in this case its not clear while reading what null actually is for so maybe it should be declared first?
|
Moving this to RFC2, draft. More work to do for sure, but we're waaaaay closer to the end than the start and I believe we've fully understood the problem domain and are narrowing in on details now. Massive props and excellent work to @robrichard for his continued championship and work on this RFC |
* Spec edits for incremental delivery, Section 3 * re-order arguments * Apply suggestions from code review Co-authored-by: Benjie <[email protected]> * Address PR feedback * Address PR feedback * Update spec/Section 3 -- Type System.md Co-authored-by: Benoit 'BoD' Lubek <[email protected]> * Update response terminology * Use new execution result terminology * Update order of arguments on @stream * field error -> execution error * update argument order in examples * _subsequent execution result_ > _execution update result_ * Update note to normative section * fix title and link * review feedback --------- Co-authored-by: Benjie <[email protected]> Co-authored-by: Benoit 'BoD' Lubek <[email protected]>
Initial Execution Result > Initial Incremental Stream Result Execution Update Result > Incremental Stream Update Result
…tal stream update result_
8e9cbcb to
fea9349
Compare
Spec draft of
@deferbased on the response format in graphql/defer-stream-wg#69, with no duplication of fields.@streamwill be added soon.Please keep discussion limited to specifics on how the spec text is written. There is a dedicated discussion forum for questions, feedback, and comments on defer & stream: https://github.com/graphql/defer-stream-wg/discussions