Sylvain

No worries thanks for letting me know. I'm not maintaining this library anymore, however I'm happy to accept pull requests if you have a fix for it.

Hey @janpio, thanks for letting me know! Removing `@prisma/sdk` entirely from Prisma-AppSync will not be an issue, as I’m only using it for its `parseEnvValue` function (which I was planning...

@Jolg42 Thanks! Will look into it.

> This looks like a good structure, would the generated revolvers be similar ? @DregondRahl Yes! Keeping the same generated resolvers, GraphQL schema and docs. Only changing the "developer-facing" API.

@ameerulislam yes, big work in progress on this repo, including CDK v2 and lots of new features. If you are curious about what’s coming next, you can have a look...

I suggest you avoid reading values from the Parameter Store at runtime (directly from within the Lambda Function), as this might incur [additional charges](https://www.amazonaws.cn/en/systems-manager/pricing/) and there are throughput limits in...

Hey @ryparker - Thanks for the PR, I'll have a proper look at it! Just to let you know, I am currently working on a huge rewrite - which will...

Instead of `beforeResolve` I would suggest leveraging the [Prisma Client Middleware](https://www.prisma.io/docs/concepts/components/prisma-client/middleware) component. Example (not tested): ```typescript // initialise prisma-appsync client const app = new PrismaAppSync({ /****/ }) // before calling...

That's a good point indeed. I've added your request to the roadmap for next release!

Since Prisma-AppSync only acts as a wrapper around Prisma Client, you should be able to take advantage of MongoDB support by upgrading the package.json to the latest version of Prisma...