Add Context types for graphql-ts export

[dcousens]

This pull request adds support for the capability to add : Context as a type refinement when doing GraphQL extensions.
Fundamentally this is still no different to a cast of as Context.

For the future, we will look at things like #7733, but for now this will be an improvement for many using these types.

export const extendGraphqlSchema = graphql.extend(base => {
  ... = graphql.object<{ authorId: string }>()({
    name: 'Statistics',
    fields: {
      authorPosts: graphql.field({
        type: graphql.Int,
        resolve({ authorId }, args, context: Context) { // <-- adding `: Context` now contextualizes the types
          return context.db.Post.count({
            where: { 
              author: {
                id: {
                  equals: authorId
                }
              }
          });
        },
      }),
    },
  })
})

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated
keystone-next-docs	✅ Ready (Inspect)	Visit Preview	Sep 1, 2022 at 7:12AM (UTC)

[changeset-bot]

🦋 Changeset detected

Latest commit: 01cfbc0

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
@keystone-6/core	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[codesandbox-ci]

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

Latest deployment of this branch, based on commit 01cfbc0:

Sandbox	Source
@keystone-6/sandbox	Configuration