context.db should not omit types omitted from the GraphQL schema

[mikehazell]

The keystone List documentation says:

omit (default: undefined): Allows you to configure which parts of the CRUD API are autogenerated for your GraphQL API …

.. but this none-the-less affects the types of context.db

const SomeList = list({
  graphql: {
    omit: {
      create: true
    },
  },
  fields: {
    someFieldName: text({
      label: '...',
    }),
  },
})

context.db.SomeList.create({
  data: { ... }
})

The .data type in db.SomeList.create results in a never, which is unnecessary.
This pull request fixes that.

[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 0f89bb9:

Sandbox	Source
@keystone-6/sandbox	Configuration

[mikehazell]

@dcousens for the record. The type error is not "the method is 'undefined'".

I get this:

Type '{ ... input data  ... }' is not assignable to type 'never'.ts(2322)
context.d.ts(107, 18): The expected type comes from property 'data' which is declared here on type '{ readonly data: never; }'