Skip to content

Fix links to graphql spec #26

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.

Sign up for GitHub

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

Merged
merged 1 commit into from
Oct 16, 2019
Merged

Fix links to graphql spec #26

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions content/documentation/master/execution.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -187,7 +187,7 @@ to include them.
To ensure you get a JSON result that conforms 100% to the graphql spec, you should call `toSpecification` on the result and then
send that back as JSON.

This will ensure that the result follows the specification outlined in http://facebook.github.io/graphql/#sec-Response
This will ensure that the result follows the specification outlined in https://graphql.github.io/graphql-spec/draft/#sec-Response


{{< highlight java "linenos=table" >}}
Expand Down Expand Up @@ -304,7 +304,7 @@ The data fetcher here is responsible for executing the mutation and returning so
// be maps. You can convert them to POJOs inside the data fetcher if that
// suits your code better
//
// See http://facebook.github.io/graphql/October2016/#sec-Input-Objects
// See https://graphql.github.io/graphql-spec/draft/#sec-Input-Objects
//
Map<String, Object> episodeInputMap = environment.getArgument("episode");
Map<String, Object> reviewInputMap = environment.getArgument("review");
Expand Down Expand Up @@ -466,10 +466,10 @@ have to do *enemies* first followed by *friends*, which would be less efficient.
It will however assemble the results in order. The query result will follow the graphql specification and return object values
assembled in query field order. Only the execution of data fetching is free to be in any order.

This behaviour is allowed in the graphql specification and in fact is actively encouraged http://facebook.github.io/graphql/#sec-Query
This behaviour is allowed in the graphql specification and in fact is actively encouraged https://graphql.github.io/graphql-spec/draft/#sec-Query
for read only queries.

See `specification <http://facebook.github.io/graphql/#sec-Normal-evaluation>`_ for details.
See `specification <https://graphql.github.io/graphql-spec/draft/#sec-Normal-and-Serial-Execution>` for details.


## AsyncSerialExecutionStrategy
Expand Down