Add a new docs page for the ApplyTransforms step. Add a new section i…

…n the each step docs with more example usage. Add a new section in PgSelect to link to each and applyTransforms to describe additional behavior a user may be interested in

grafast/website/grafast/step-library/dataplan-pg/pgSelect.md

@@ -404,3 +404,14 @@ expect, instead it uses a tuple with entries for each of the selected
 attributes. The makeup of this tuple will vary depending on which attributes
 you requested, and in which order, so you must not rely on its structure. To
 get an attribute you should use `$pgSelectSingle.get(attr)` or similar
+
+## Using the Underlying Data of a PgSelect Step
+
+Although PgSelect is an opaque step, there are a few ways to modify the keys and values of that are returned in the plan. 
+
+For altering the returned keys of the object, see the documentation for [`each`](../standard-steps/each.md)
+
+For altering the values of the returned object, see the documentation for [`applyTransforms`](../standard-steps/applyTransforms.md)
+
+
+

grafast/website/grafast/step-library/standard-steps/applyTransforms.md

@@ -0,0 +1,51 @@
+# applyTransforms
+
+Takes a step as the first argument and returns a step that guarantees all `listItem` transforms have occurred.
+
+This step is useful for when you need all of:
+ * the `listItem` transforms to have already taken place (e.g. you're going to
+ * send the result to an external service) rather than processing them through
+ * the GraphQL response
+
+ This is very useful for modifying the values of an opaque step!
+
+
+## Type
+
+```ts
+function applyTransforms(
+  $step: ExecutableStep
+): ExecutableStep<any>;
+```
+
+### Example
+
+Let's say you have a `PgSelect` step and you want to apply logic to the values of said step. You may be inclined to do something like this:
+
+```ts
+const $users = usersResource.find();
+const tbl = $users.alias;
+$users.where(sql`${tbl}.username = 'Benjie'`);
+// Options that could be used here include: loadOne, loadMany, lambda
+return lambda($users, (users) => {
+    return users.map(user => ({
+        username: 'USER-' + user.username,
+        ...user,
+    }))
+}, true);
+```
+
+Due to `PgSelect` being an opaque step, this will not work! The values of `$users` will not be loaded by the time the `lambda` step is run. In order to guarantee that those values are available, you can wrap the `$users` step in an `applyTransforms`!
+
+```ts
+const $users = usersResource.find();
+const tbl = $users.alias;
+$users.where(sql`${tbl}.username = 'Benjie'`);
+// By using applyTransforms, it guarantees these values will be available
+return lambda(applyTransforms($users), (users) => {
+    return users.map(user => ({
+        username: 'USER-' + user.username,
+        ...user,
+    }))
+}, true);
+```

grafast/website/grafast/step-library/standard-steps/each.md

@@ -7,3 +7,36 @@ Usage:
 ```ts
 const $newList = each($oldList, ($listItem) => doSomethingWith($listItem));
 ```
+
+## Extended Usage with `object`
+
+You may end up in a scenario where you need to alter the return value of an opaque step. For example, when using a `PgSelect` step, you may end up with something like this in your plan:
+
+```ts
+const $users = usersResource.find();
+const tbl = $users.alias;
+$users.where(sql`${tbl}.username = 'Benjie'`);
+return $users;
+```
+
+For this example, lets say you have a field you want to resolve to with a type that does not match the schema of the DB:
+
+```graphql
+type UsernameMapping {
+  currentUsername: String!;
+  currentEmail: String!;
+}
+
+```
+
+In order to map these values to new keys, you could use something like this:
+
+```ts
+// return $users;
+return each($users, ($user) => 
+    object({
+        currentUsername: $user.get('username'),
+        currentEmail: $user.get('email')
+    })
+)
+```