Update validation page. #1803
Update validation page. #1803
Conversation
|
@mandiwise is attempting to deploy a commit to the The GraphQL Foundation Team on Vercel. A member of the Team first needs to authorize it. |
|
|
||
| ```graphql | ||
| # { "graphiql": true } | ||
| # INVALID: favoriteSpaceship does not exist on Character | ||
| { | ||
| query { |
There was a problem hiding this comment.
Interested to know why you're moving away from the query shorthand here? It tends to be very rare that I see this - either the operation has a name and/or variables in which case you need query, or it has neither in which case it's very rare to see it in my experience.
There was a problem hiding this comment.
I've tended to see the opposite (inclusion of the query keyword) so I included it for clarity after all of the keywords are introduced on the operation pages. But I can remove it throughout if the shorthand syntax is the preferred convention.
There was a problem hiding this comment.
Let's worry about that afterwards, if at all; it's much easier to replace /^query {$/ with { than the reverse - so keep going with the query keyword for now.
Interesting that your experience differs; I wonder what the ecosystem as a whole sees!
Co-authored-by: Benjie <benjie@jemjie.com>
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Co-authored-by: Benjie <benjie@jemjie.com>
Co-authored-by: Benjie <benjie@jemjie.com>
Description
This PR contains updated validation content for the Learn docs. Key changes include:
@benjie @jorydotcom