middy-appsync

Middy Middleware for Aws AppSync.

Install

npm install --save middy-appsync

Purpose

This middleware follows the recommendations from the official AppSync documentation. It wraps the handler's response into a GraphQl Response object of the following shape:

{
  data: Object,
  errorMessage: string,
  errorType: string,
  errorInfo: Object
}

You can then use it in your response template like so:

#if( $context.result && $context.result.errorMessage )
    $utils.error($context.result.errorMessage, $context.result.errorType, $context.result.data, $context.result.errorInfo)
#else
    $utils.toJson($context.result.data)
#end

If errorMessage is present, it will generate a GraphQl error. Otherwise, the data field will be returned by the resolver to your field.

The midleware automatically wraps a successful response from the lambda function into the data field and any error to the error* fields.

Usage

Basic usage

const middy = require('middy');
const { appSync } = require('middy-appsync');
 
const doStuff = (event, context, callback) => {
  callback(null, {
    field1: 'Foo',
    field2: 'Bar',
  });
};
 
const handler = middy(doStuff)
  .use(appSync());
 
module.exports = { handler };

Will output

{
  data: {
    field1: 'Foo',
    field2: 'Bar',
  }
}

Error handling

When a "controlled" error occurs during the execution of your handler, you want to send basic information to the user. You can do so by filling the errorMessage, errorType and errorInfo fields.

You can acheive that with the a GraphQlError object in different ways:

Using the callback function

• throw a GraphQlError
• return it as the error argument
• return it as the response argument

Using promises/async

• throw a GraphQlError
• return it as the rejected value
• return it as the resolved value

Notes:

Resolving or returning any Error other than GraphQlError as a response will be handled by the middleware but the errorMessage will be concealed into a "generic" Internal Server Error. This is a prevention measure only in order to avoid leaking sensitive data. It is not recommended to return any other Error than GraphQlError as a response.

Throwing or rejecting any Error other than GraphQlError will not be handled by the middleware and be treated a "normal" Error. You will still need to handle it yourself (e.g: in another middlware).

Example:

const middy = require('middy');
const { appSync, GraphQlError } = require('middy-appsync');
 
const doStuff = (event, context, callback) => {
  callback(new GraphQlError('Record not found', 'NotFoundError'));
};
 
const handler = middy(doStuff)
  .use(appSync());
 
module.exports = { handler };

Will output

{
  errorMessage: 'Record not found',
  errorType: 'NotFoundError',
  data: null,
  errorInfo: null
}

BatchInvoke support

The middleware supports Batching resolvers. If it detects that the event object is an array, it will expect an array as response from the handler and wrap each of its elements into a GraphQl response object.

If the response is not an array or its length is different from the event's length, it will throw an Error.

const middy = require('middy');
const { appSync } = require('middy-appsync');
 
// event is an array
const doStuff = (event, context, callback) => {
  callback(null, [
    { title: 'Foo', content: 'Bar' },
    { title: 'Bizz', content: 'Bazz' },
  ]);
};
 
const handler = middy(doStuff)
  .use(appSync());
 
module.exports = { handler };

Will output

[
  {
    data: {
      title: 'Foo',
      content: 'Bar',
    }
  },
  {
    data: {
      title: 'Bizz',
      content: 'Bazz',
    }
  },
]

BatchInvoke error handling

Just like for normal handlers, throwing a GraphQlError or returning it in the first argument of the callback will return the error in the errors blocks. It is worth mentioning that, by doing so, the error will be replicated to all elements of the batch (making the full batch invalid).

In order to have individual control over which elements of the batch are valid or have errors, you can return a GraphQlError for the invalid elements.

Example:

const middy = require('middy');
const { appSync, GraphQlError } = require('middy-appsync');
 
const doStuff = (event, context, callback) => {
  callback(null, [
    new GraphQlError('Post not found', 'NotFound'), // first element is Invalid
    { title: 'Bizz', content: 'Bazz' }, // second element is valid
  ]);
};
 
const handler = middy(doStuff)
  .use(appSync());
 
module.exports = { handler };

Will output

[
  {
    errorMessage: 'Post not found',
    errorType: 'NotFound',
    data: null,
    errorInfo: null
  },
  {
    data: {
      title: 'Bizz',
      content: 'Bazz',
    }
  },
]

Caveats

AppSync currently does not implement the GraphQl specs properly for the Errors entry. This middleware is currently limited to AppSync's implementation, using the message, errorType, data and errorInfo, entries. There is an open issue on AppSync for this.