Define Data Collections used in the spec #1091
Closed
+37
−2
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
benjie
added
the
✏️ Editorial
✅ Deploy Preview for graphql-spec-draft ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
benjie
added
📄 Draft (RFC 2)
|
This was split from RFC2 PR #1063, so I have marked it as RFC 2 itself. |
JoviDeCroock
approved these changes
Jun 7, 2024
|
Oops, apparently I pushed to a branch on the spec itself rather than my fork, hence this was out of date. Fixed. |
|
Moved to a branch on the GitHub spec repo directly: #1102 |
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.
The spec uses the terms "set", "list" and "map" in many places. This PR defines these terms and their conformance requirements.
This is a change extracted from #1063 as discussed at last night's WG meeting
The next PR in this stack is:
cc @graphql/tsc