Add ‘best practices’ specs to agenda and myself to attendees. #50
Conversation
This file contains hidden or 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
IvanGoncharov
added a commit
to graphql/graphql-spec
that referenced
this pull request
Jul 1, 2021
Background graphql/graphql-wg#50 graphql-js PR graphql/graphql-js#3208
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.
Not entirely sure this is the right venue for it, but proposing just in case.
In short, I’d like to propose detaching the Connections and Global Object Identification specifications from the ‘Relay’ brand and move them into a ‘best practices’ specifications repo that’s closer to the GraphQL brand, because my experience is that people avoid these for the wrong reasons.
Here’s an older comment of my proposal that has seen some upvotes.