Sacha Greif

I did find https://www.prisma.io/docs/reference/prisma-api/queries-ahwee4zaey/#pagination, I assume it would work the same way? What about Relay-style pagination? I'm not very familiar with it but is it worth considering?

Just to clarify, I think a better example would be: - multiple arguments: ``` updateUser(where: { id: "1" }, data: { name: "Karl" }) ``` - single argument: ``` updateUser(input:...

For the payload I agree, but I was talking with @schickling and @sorenbs and we weren't sure if that pattern also made sense for the input.

I think I'm leaning towards not following that pattern. My mutations have at most 2 arguments anyway so I don't think it's worth adding that extra level of indirection all...

Found another one: https://github.com/Intelight/graphql-crud

I found one here: ``` enum UserOrderByInput { # ascending and descending for all non-list scalar fields } query { users(orderBy: UserOrderByInput): [User!]} query { users(orderBy: NAME_ASC) {name}} ``` I...

See also: https://dev-blog.apollodata.com/designing-graphql-mutations-e09de826ed97 Personally I think it's a useful feature, I've had cases where I've needed to return additional data with a mutation result (for example, errors or warnings) and...

At its most basic a search spec would need to include a `keyword` property. I guess there could also be options such as `caseSensitive`, `fuzzy`…? Also, should the spec support...

Thanks, that's really helpful!

Oh right. Currently we get those descriptions through our own API which makes it a little harder to get the correct language. I think for now we can leave them...