fix: jest exits after tests run

[shreyas44]

• Use the Prisma Client created in db.ts in the API Context
• Disconnect Prisma Client after running each test, allowing Jest to exit. Previously this was an issue as the Prisma Client connection was never closed and prevent Jest from exiting. This issue was fixed yesterday in a9ca189
  using a workaround by passing the --forceExit flag to Jest.

This PR adds a proper fix for graphql-nexus/nexus#678.

[shreyas44]

Is there a reason we're passing a function as the context instead of just passing a regular Object?

[jasonkuhrt]

Because a function is what Apollo Server expects. It is called on every request. Usually work is done here to expose request scoped details to resolvers, like current user.

This needs to be explained better in the tutorial.

[shreyas44]

Usually work is done here to expose request scoped details to resolvers, like current user.

Yup, I've actually done that in an app I'm building.

Because a function is what Apollo Server expects.

Apollo Server actually expects either a function or a plain javascript object. It's not really a big deal, but I thought it might've been simpler just passing a context object in this case.

[jasonkuhrt]

Good to know, in the spirit of the tutorial that incrementally builds up on an as-needed basis I would happily accept a PR to make this change!

[shreyas44]

Done!

graphql-nexus/nexus#718

[jasonkuhrt]

ty!