From ce67f4c99398013ba61d6fe8be3de35eef8ac0d6 Mon Sep 17 00:00:00 2001 From: Grant Carthew Date: Tue, 29 Nov 2016 12:38:16 +1000 Subject: [PATCH] Update Guides-ConstructingTypes.md Removed repeat of the start of the sentence. --- site/graphql-js/Guides-ConstructingTypes.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/site/graphql-js/Guides-ConstructingTypes.md b/site/graphql-js/Guides-ConstructingTypes.md index 45a5e3dc47..9abd6e100d 100644 --- a/site/graphql-js/Guides-ConstructingTypes.md +++ b/site/graphql-js/Guides-ConstructingTypes.md @@ -8,7 +8,7 @@ next: /graphql-js/express-graphql/ For many apps, you can define a fixed schema when the application starts, and define it using GraphQL schema language. In some cases, it's useful to construct a schema programmatically. You can do this using the `GraphQLSchema` constructor. -When you are using the `GraphQLSchema` constructor to create a schema, instead of defining `Query` and `Mutation` types solely using schema language, you create them as separate object types using the `GraphQLObjectType` constructor. +When you are using the `GraphQLSchema` constructor to create a schema, instead of defining `Query` and `Mutation` types solely using schema language, you create them as separate object types. For example, let's say we are building a simple API that lets you fetch user data for a few hardcoded users based on an id. Using `buildSchema` we could write a server with: