-
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
[Docs] Should this section in Relay's docs be moved to GraphQL.org? #131
Comments
Perhaps we'll consider this as we expand documentation to include a "best practices" section. Right now Relay is the only tool which requires connections to be modeled in this way, which is why those documentation details are in a Relay specific place. But we think connections are a good idea in general that many GraphQL backends could take advantage of. |
@leebyron I don’t know if this is my unique experience, but too often I end up having to explain to newcomers that these are not just for Relay, but instead a convention that’s indeed a good idea in general. While I personally love Relay, the connection to Relay (no pun intended) really seems to ruffle people’s feathers in such a way that they actively decide to not use connections, without apparently understanding the full benefits. Instead what I usually hear is a lament about having to do ‘more’ work for Relay when creating their schemas. While I understand that the GraphQL spec may not be the right place to describe conventions, I would really like to see such convention specs be detached from Relay and where possible move closer to where the GraphQL spec lives. (The same applies to the Global Object Identification specification btw.) |
https://facebook.github.io/relay/docs/graphql-connections.html#content
The text was updated successfully, but these errors were encountered: