From 69acbd7a99ddcdcb3f8ab2b88725d921707bb49b Mon Sep 17 00:00:00 2001 From: whysage Date: Wed, 13 Apr 2022 10:24:40 +0300 Subject: [PATCH] docs: fix data/errors block --- src/content/learn/BestPractice-ServingOverHTTP.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/learn/BestPractice-ServingOverHTTP.md b/src/content/learn/BestPractice-ServingOverHTTP.md index a67e896e7b..37f71dad9c 100644 --- a/src/content/learn/BestPractice-ServingOverHTTP.md +++ b/src/content/learn/BestPractice-ServingOverHTTP.md @@ -69,7 +69,7 @@ Regardless of the method by which the query and variables were sent, the respons } ``` -If there were no errors returned, the `"errors"` field should not be present on the response. If no data is returned, [according to the GraphQL spec](http://facebook.github.io/graphql/#sec-Data), the `"data"` field should only be included if the error occurred during execution. +If there were no errors returned, the `"errors"` field should not be present on the response. If no data is returned, [according to the GraphQL spec](http://facebook.github.io/graphql/#sec-Data), the `"data"` field should only be included if no errors occurred during execution. ## GraphiQL GraphiQL is useful during testing and development but should be disabled in production by default. If you are using express-graphql, you can toggle it based on the NODE_ENV environment variable: