Add API docs for the list items API

[timleslie]

Adds docs for the lists item API. Preview here: https://keystone-next-docs-git-items-api-docs-keystonejs.vercel.app/apis/list-items

Updates the findMany() and count() functions to have a default arg of {} so that .count() and .findMany() work as expected when no argument is provided.

Updates an arbitrary handful of server-side-graphql-client calls in the tests to use the list items API to verify that the documents can be followed successfully. This is the first set of changes for #5485.

Does not document the DB items API, that will be done separately.

[changeset-bot]

🦋 Changeset detected

Latest commit: b4574b5

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

This PR includes changesets to release 5 packages

Name	Type
@keystone-next/keystone	Patch
@keystone-next/types	Patch
@keystone-next/test-utils-legacy	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

[vercel]

This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployment, click below or on the icon next to each commit.

🔍 Inspect: https://vercel.com/keystonejs/keystone-next-docs/4H8dC44juawSqwsdoQDciG3WKHaz
✅ Preview: https://keystone-next-docs-git-items-api-docs-keystonejs.vercel.app

[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 b4574b5:

Sandbox	Source
@keystone-next/example-sandbox	Configuration

[JedWatson]

Great start @timleslie 👏

Not required for this PR (good to publish this immediately imo) but a couple of next steps stood out when I was reading:

• You're demo'ing the API for relationship creation, I don't think we've actually documented this anywhere else and it's a bit like "oh wait, what's that doing? how do I learn more? what else can I do?" and it would be good to add a link out when there's more docs for that
• For the create/update mutation APIs, would be nice to add some explanation for what the data argument actually is; this subtly doesn't match the output types people may expect, again I think the API reference for this is missing though and people will probably wonder about that here, it's a bit mysterious
• We're not explaining anything about how permissions (/ session) interact here. That's kind of covered in the context API docs, but would probably be good to remind readers about here because it's usually going to be related and important to think about when using this API

[timleslie]

Great start @timleslie 👏

Not required for this PR (good to publish this immediately imo) but a couple of next steps stood out when I was reading:

• You're demo'ing the API for relationship creation, I don't think we've actually documented this anywhere else and it's a bit like "oh wait, what's that doing? how do I learn more? what else can I do?" and it would be good to add a link out when there's more docs for that

Yep, that's on my hit list 👍

• For the create/update mutation APIs, would be nice to add some explanation for what the data argument actually is; this subtly doesn't match the output types people may expect, again I think the API reference for this is missing though and people will probably wonder about that here, it's a bit mysterious

We have rudimentary API docs for the GraphQL operations here: https://next.keystonejs.com/apis/graphql#create-user I might go ahead and link do these docs.

• We're not explaining anything about how permissions (/ session) interact here. That's kind of covered in the context API docs, but would probably be good to remind readers about here because it's usually going to be related and important to think about when using this API

Yep, will loop back on that once those guides and APIs are more fleshed out 👍