feat(event-handler): Add includeRouter support to AppSync GraphQL resolver

[arnabrahman]

Summary

This PR adds the ability for router composition

Changes

Follows the implementation provided in the linked issue description. Removed context sharing as discussed

• includeRouter method for router composition
• 100% unit test coverage
• Documentation added, mostly followed what we have in python documentation

// Schema
type Post {
	id: ID
	title: String
	content: String
}

type User {
	id: ID
	name: String
	email: AWSEmail
}

type Query {
	getUsers: [User]
	getPosts: [Post]
}

schema {
	query: Query
}

//postRouter.ts
import { Router } from '@aws-lambda-powertools/event-handler/appsync-graphql';

const postRouter = new Router();

postRouter.onQuery('getPosts', async (args) => {
  return [{ id: 1, title: 'First post', content: 'Hello world!' }];
});

export { postRouter };

// userRouter.ts
import { Router } from '@aws-lambda-powertools/event-handler/appsync-graphql';

const userRouter = new Router();

userRouter.onQuery('getUsers', async (args) => {
  return [{ id: 1, name: 'John Doe', email: 'john@example.com' }];
});

export { userRouter };

// app.ts
import { AppSyncGraphQLResolver } from '@aws-lambda-powertools/event-handler/appsync-graphql';
import { Logger } from '@aws-lambda-powertools/logger';
import type { Context } from 'aws-lambda';
import { userRouter } from './userRouter.js';
import { postRouter } from './todoRouter.js';

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

app.includeRouter([userRouter, postRouter]);

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

query MyQuery {
  getUsers {
    id,
    name,
    email
  }
}

{
  "data": {
    "getUsers": [
      {
        "id": "1",
        "name": "John Doe",
        "email": "john@example.com"
      }
    ]
  }
}

query MyQuery {
  getPosts {
    id,
    title,
    content,
  }
}

{
  "data": {
    "getPosts": [
      {
        "id": "1",
        "title": "First post",
        "content": "Hello world!"
      }
    ]
  }
}

Issue number: closes #4131

---

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.

[dreamorosi]

We have updated the linting rules of the project to make them a bit stricter - this should make reviewing contributions easier on both sides since you can now catch issues both with pre-commit hooks and CI here on the PR.

You might need to rebase and address the issues in the new code to get the CI green.

[dreamorosi]

@sdangol / @svozza can you please follow this PR while I'm away?

Been chatting with @arnabrahman on Discord and he's blocked with a question we need to answer in #4131 - after this he's probably going to be able to move forward.

[svozza]

One small comment but other than that LGTM!

[svozza]

Fantastic work as always @arnabrahman!

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

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

See analysis details on SonarQube Cloud