From 4a096b14ecdd67c0d30e4d7f9559e94efbedab70 Mon Sep 17 00:00:00 2001
From: "David B. Nagle" <nagledb@gmail.com>
Date: Fri, 2 Nov 2018 21:10:54 -0700
Subject: [PATCH] Restore "Defining resolvers" documentation

Content was inadvertently removed in d6add77540d3133fe4829da6fc863c5cd48efbe2
---
 docs/type-system/type-language.md | 24 ++++++++++++++++++++++++
 1 file changed, 24 insertions(+)

diff --git a/docs/type-system/type-language.md b/docs/type-system/type-language.md
index 57c9960..8f1c06f 100644
--- a/docs/type-system/type-language.md
+++ b/docs/type-system/type-language.md
@@ -38,6 +38,30 @@ By default, such schema is created without any resolvers.
 We have to rely on [default field resolver](../data-fetching.md#default-field-resolver) and **root value** in 
 order to execute a query against this schema.
 
+# Defining resolvers
+Since 0.10.0
+
+In order to enable **Interfaces**, **Unions** and custom field resolvers you can pass the second argument:
+**type config decorator** to schema builder.
+
+It accepts default type config produced by the builder and is expected to add missing options like
+[**resolveType**](interfaces.md#configuration-options) for interface types or
+[**resolveField**](object-types.md#configuration-options) for object types.
+
+```php
+<?php
+use GraphQL\Utils\BuildSchema;
+
+$typeConfigDecorator = function($typeConfig, $typeDefinitionNode) {
+    $name = $typeConfig['name'];
+    // ... add missing options to $typeConfig based on type $name
+    return $typeConfig;
+};
+
+$contents = file_get_contents('schema.graphql');
+$schema = BuildSchema::build($contents, $typeConfigDecorator);
+```
+
 # Performance considerations
 Since 0.10.0