cleanup

Author: ddebrunner

protection/jwt-claims/README.md

@@ -23,7 +23,7 @@ from being executed by field visibility and access rules.
 Instead a field `Query.me` is exposed with no field arguments that invokes `Query.customer`
 with the customer identifier pulled from the `sub` claim in the request's JWT.
 
-This is implemented using `@sequence` with the first step an intermediate field (`Query._myid`) that is annotated with `@value` using an ECMAScript.
+This is implemented using `@sequence` with the first step an intermediate field (`Query._myid`) that is annotated with `@value` using ECMAScript.
 This script has access to field arguments of its annotated field (in this case none) and JWT claims through `$jwt`.
 Thus it returns the `sub` claim which is then automatically mapped as a scalar value to the sole argument of
 the next step in the sequence (`Query.customer(id:)`).

protection/jwt-claims/api.graphql

@@ -5,6 +5,9 @@ type Customer {
 }
 
 type Query {
+  """
+  Fetch customer by identifier.
+  """
   customer(id: ID!): Customer
     @dbquery(
       type: "postgresql"
@@ -13,6 +16,10 @@ type Query {
       configuration: "postgresql_config"
     )
 
+  """
+  Fetch my customer information.
+  Customer identifier is pulled from the JWT subject claim.
+  """
   me: Customer @sequence(steps: [{ query: "_myid" }, { query: "customer" }])
 
   """