From c57bbabb3ac730af29cd414b3e1cd8b01245c857 Mon Sep 17 00:00:00 2001 From: Robert Holloway Date: Fri, 24 May 2019 08:25:09 -0600 Subject: [PATCH] Last paragraph of the file not correct. The last paragraph of the resolvers.md file is not accurate. It states that the next section will be "...about testing your graph." However, the next section linked is "4. Run your graph in production". I would propose that the graph testing actually be put as the next section instead of how to run in production. --- docs/source/tutorial/resolvers.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/source/tutorial/resolvers.md b/docs/source/tutorial/resolvers.md index 65c660b..5bc63ef 100644 --- a/docs/source/tutorial/resolvers.md +++ b/docs/source/tutorial/resolvers.md @@ -419,4 +419,4 @@ Next, paste our authorization header into the HTTP Headers box at the bottom: } ``` -Then, run the mutation. You should see a success message, along with the ids of the mutations we just booked. Testing mutations manually in the playground is a good way to explore our API, but in a real-world application, we should run automated tests so we can safely refactor our code. In the next section, you'll learn all about testing your graph. +Then, run the mutation. You should see a success message, along with the ids of the mutations we just booked. Testing mutations manually in the playground is a good way to explore our API, but in a real-world application, we should run automated tests so we can safely refactor our code. In the next section, you'll actually learn about running your graph in production instead of testing your graph.