Updating documentation.

Author: fubhy

doc/SUMMARY.md

@@ -23,8 +23,3 @@
 ## Mutations
 
 * [Mutations](mutations/README.md)
-
-## Advanced
-
-* [Split up schema](advanced/split-schema.md)
-

doc/advanced/split-schema.md

@@ -142,25 +142,20 @@ To add the resolvers we go to our schema implementation and call the created dat
 
 ```php
 /**
-   * {@inheritdoc}
-   */
-  protected function getResolverRegistry() {
-    
-    ...
-
-    // Create article mutation.
-    $registry->addFieldResolver('Mutation', 'createArticle',
-      $builder->produce('create_article', [
-        'mapping' => [
-          'data' => $builder->fromArgument('data'),
-        ],
-      ])
-    );
-
-    ...
-
-    return $registry;
-  }
+ * {@inheritdoc}
+ */
+protected function getResolverRegistry() {
+  
+  ...
+  // Create article mutation.
+  $registry->addFieldResolver('Mutation', 'createArticle',
+    $builder->produce('create_article')
+      ->map('data', $builder->fromArgument('data'))
+  );
+
+  ...
+  return $registry;
+}
 ```
 
 This mutation can now be called like this :

doc/mutations/README.md

@@ -25,15 +25,12 @@ We are telling the schema that we have a new field on the "Article" type called
 The following code is an example of how a data producer for a creator field on the Article type can be implemented in code.
 
 ```php
-    $registry->addFieldResolver('Article', 'creator',
-      $builder->produce('property_path', [
-        'mapping' => [
-          'type' => $builder->fromValue('entity:node'),
-          'value' => $builder->fromParent(),
-          'path' => $builder->fromValue('field_article_creator.value'),
-        ],
-      ])
-    );
+$registry->addFieldResolver('Article', 'creator',
+  $builder->produce('property_path')
+    ->map('type', $builder->fromValue('entity:node'))
+    ->map('value', $builder->fromParent())
+    ->map('path', $builder->fromValue('field_article_creator.value'))
+);
 ```
 
 Essentially this is what you need to do every time you want to make a field available in the schema. We tell Drupal where and how to get the data and specify where this maps to.

doc/producers/README.md

@@ -6,13 +6,10 @@ This can be accomplished using some of the built-in helpers inside the `$builder
 
 ```php
 $registry->addFieldResolver('Query', 'currentUser', $builder->compose(
-    $builder->produce('current_user'),
-    $builder->produce('entity_load', [
-        'mapping' => [
-            'type' => $builder->fromValue('user'),
-            'id' => $builder->fromParent(),
-        ],
-    ])
+  $builder->produce('current_user'),
+  $builder->produce('entity_load')
+    ->map('type', $builder->fromValue('user'))
+    ->map('id', $builder->fromParent())
 ));
 ```
 
@@ -24,16 +21,13 @@ What if we need to do some massaging but not necessarily using any data producer
 
 ```php
 $registry->addFieldResolver('Query', 'currentUser', $builder->compose(
-    $builder->produce('current_user'),
-    $builder->produce('entity_load', [
-        'mapping' => [
-            'type' => $builder->fromValue('user'),
-            'id' => $builder->fromParent(),
-        ],
-    ]),
-    $builder->callback(function ($entity) {
-        // Here we can do anything we want to the data. We get as a parameter anyting that was returned
-        // in the previous step.
-    })
+  $builder->produce('current_user'),
+  $builder->produce('entity_load')
+    ->map('type', $builder->fromValue('user'))
+    ->map('id', $builder->fromParent()),
+  $builder->callback(function ($entity) {
+    // Here we can do anything we want to the data. We get as a parameter anyting that was returned
+    // in the previous step.
+  })
 ));
 ```

doc/producers/composing.md

@@ -103,13 +103,10 @@ Lets see how we can consume our newly created data producer :
 
 ```php
 $registry->addFieldResolver('Query', 'currentUser', $builder->compose(
-    $builder->produce('current_user'),
-    $builder->produce('entity_load', [
-        'mapping' => [
-            'type' => $builder->fromValue('user'),
-            'id' => $builder->fromParent(),
-        ],
-    ])
+  $builder->produce('current_user'),
+  $builder->produce('entity_load')
+    ->map('type', $builder->fromValue('user'))
+    ->map('id', $builder->fromParent())
 ));
 ```
 

doc/producers/custom.md

@@ -17,13 +17,10 @@ type Article implements NodeInterface {
 We now need to resolve the title field via a data producer which is already provided by the `entity_label` module. This will give us the label of an entity:
 
 ```php
-    $registry->addFieldResolver('Article', 'title',
-      $builder->produce('entity_label', [
-        'mapping' => [
-          'entity' => $builder->fromParent(),
-        ],
-      ])
-    );
+$registry->addFieldResolver('Article', 'title',
+  $builder->produce('entity_label')
+    ->map('entity' => $builder->fromParent())
+);
 ```
 
 We can now run a query like this: