-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Incremental Delivery spec draft #1110
Open
robrichard
wants to merge
40
commits into
graphql:main
Choose a base branch
from
robrichard:robrichard/defer-stream-v2
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
+1,253
−82
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
✅ Deploy Preview for graphql-spec-draft ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Hi @robrichard , do you have any expected timeline for this feature? We are really excited to have this feature for our product! |
benjie
added
💭 Strawman (RFC 0)
RFC Stage 0 (See CONTRIBUTING.md)
💡 Proposal (RFC 1)
RFC Stage 1 (See CONTRIBUTING.md)
and removed
💭 Strawman (RFC 0)
RFC Stage 0 (See CONTRIBUTING.md)
labels
Oct 15, 2024
mostly to reduce the diff.
instead of sometimes fieldGroup, for consistency and so as to remove another "Group" term
"node" should be "field" within CreateSourceEventStream Co-authored-by: Rob Richard <[email protected]>
accompanying note is a WIP, open to further suggestions as to how to clarify
…ting an Execution Plan" section
… root nodes before the graph was adjusted
* Add Response Section for defer/stream * review fixes * fix
* Add defer and stream directives to type system * Add defer/stream validation rules
robrichard
force-pushed
the
robrichard/defer-stream-v2
branch
from
November 1, 2024 15:36
9ec7f65
to
f7e9124
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Spec draft of
@defer
based on the response format in graphql/defer-stream-wg#69, with no duplication of fields.@stream
will 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