Low fidelity Typescript types for `context.query`

Steps to reproduce

Follow the docs link to create a project: How to embed Keystone + SQLite in a Next.js app.

Expected result

It builds just fine, dynamic lists typings are connected with imports.

Actual result

npm run build doesn’t work:

List item types has any type (instead of Post for query.Post.findMany):

Node v14.18.1, macOS 12.1.

Workarounds

Currently I found out that it can be “fixed” by importing from .keystone/types and specifying types manually like this, for each usage on Next.js pages on frontend:

import { query } from '.keystone/api'
import { Lists } from '.keystone/types'

export async function getStaticProps() {
  const posts = (await query.Post.findMany({ query: 'id title slug' })) as Lists.Post.Item[]
  return { props: { posts } }
}

[emmatown]

We’ve somewhat improved this with #7249 which is yet to be released and we’re looking at improving this further

[dmythro]

@dcousens thanks! Yes, complete typings implementation looks complicated for this kind of queries, but at least I’d expect this to return something like a Partial<Post> (or to be more precise, Promise<Partial<Post>>).