feat(event-handler): add support for error handling in AppSync GraphQL

[arnabrahman]

Summary

This PR adds support for error handling in AppSync GraphQL described in the issue

Changes

• exceptionHandler method is introduced to register an exception and its handler.
• ExceptionHandlerRegistry is introduced to keep track of registered exception handlers
• exceptionHandler is also exposed as a decorator method
• Unit tests are written for 100% coverage
• Added documentation for exception handling with examples
• Minor housekeeping(ex: dockerfile nodejs version update due to error & endregion added)

Lambda handler:

import { AppSyncGraphQLResolver } from '@aws-lambda-powertools/event-handler/appsync-graphql';
import { Logger } from '@aws-lambda-powertools/logger';
import { AssertionError } from 'assert';
import type { Context } from 'aws-lambda';

const logger = new Logger({
  serviceName: 'MyService',
});
const app = new AppSyncGraphQLResolver({ logger });

app.exceptionHandler(AssertionError, async (error) => {
  return {
    error: {
      message: error.message,
      type: error.name,
    },
  };
});

app.onQuery('createSomething', async () => {
  throw new AssertionError({
    message: 'This is an assertion Error',
  });
});

export const handler = async (event: unknown, context: Context) =>
  app.resolve(event, context);

APPSYNC JS resolver

export function request(ctx) {
  return {
    operation: 'Invoke',
    payload: ctx,
  };
}

export function response(ctx) {
  if (ctx.result.error) {
    return util.error(ctx.result.error.message, ctx.result.error.type);
  }
  return ctx.result;
}

Response mapping template

#if (!$util.isNull($ctx.result.error))
  $util.error($ctx.result.error.message, $ctx.result.error.type)
#end

$utils.toJson($ctx.result)

Response:

{
  "data": {
    "createSomething": null
  },
  "errors": [
    {
      "path": [
        "createSomething"
      ],
      "data": null,
      "errorType": "AssertionError",
      "errorInfo": null,
      "locations": [
        {
          "line": 2,
          "column": 3,
          "sourceName": null
        }
      ],
      "message": "This is an assertion Error"
    }
  ]
}

Issue number: closes #4130

---

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.

[leandrodamascena]

Hi @arnabrahman, thanks for responding to all the comments and making the necessary changes! We'll be back with this PR and review next week.

[dreamorosi]

Thank you for the PR and for the patience, I was meant to review this on Friday but I had some personal issues and couldn't get to it.

I've left a couple questions and a few suggestions - once they're addressed we're ready to merge.

[dreamorosi]

Thank you for working on this feature @arnabrahman - apologies if this has taken a bit longer than usual to get merged, we really appreciate your contribution!

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
4.5% Duplication on New Code

See analysis details on SonarQube Cloud

[svozza]

Fantastic work @arnabrahman. Another fine addition!