Daniel Cousens

That's an interesting consideration @Zlitus, and honestly that might mean we up with preferring this configuration being explicitly configurable by users with documentation warnings, instead of being specifically prescripted by...

Thanks for resurrecting @AlanBreck! We appreciate community feedback as it helps us know what's problematic for users :blue_heart:

Thinking about this @zizzfizzix, I think we should do everything we can to show better data seeding practices in the examples rather than in the documentation. If users are trying...

As shown in https://github.com/keystonejs/keystone/pull/7113/files, this problem is painful to resolve without duplicating your type definitions. Unfortunately the stringly-typed nature of the `.query` argument in `await query.Post.findMany({ query: 'this is not...

Unfortunately the GraphQL types are not exactly 1 to 1, so `Partial` might be OK, but not always depending on the field. This is an active point we are working...

Cannot reproduce this, but I'm wondering if this is somewhat similar to https://github.com/keystonejs/keystone/discussions/7915#discussioncomment-3696037 @moritzgvt, @Tangcuyu can you try the `/init` process using the credentials name `test`, email `test`, password `testtest`?...

@jschuur to clarify, you're saying this is only a problem if you are using `npm`, and not a problem when using `yarn`?

@jschuur, @mzsigler @joshkelly and others, please see our technical writeup for this problem in https://github.com/keystonejs/keystone/issues/7816#issuecomment-1221725768 I think I will close this issue for now as it is quite old and...

~I don't think we want to support an asynchronous configuration from the `keystone.ts`, but with new pathways like `getContext`, users should feel free to run any asynchronous actions as needed...

@pazams if you had any examples of how you are wanting to use this, that would really help us resolve this canonically for Keystone