Aurélien GEORGET

@schickling Do you have any thoughts about this? It seems the problem has been raised with Prisma (https://github.com/prismagraphql/prisma/issues/1772) as well.

We should add this to the specs though. I found [a list](http://www.englishlci.edu/blog/english-grammar-lessons/did-you-know-that-these-words-have-no-plural/) (not sure it's exhaustive) with all the words which have no plural and where we should use the...

I think the last one is easier to use (from a front-end point of view) because you've only one argument to pass, and you don't need to pick the `where`...

@SachaG Thank for the clarification! It would make more sense to keep the "top-level input argument" pattern for the input because it seems this pattern is recommended for payload as...

I tried to iterate with the example you gave me. ``` updateUser(input: { where: { id: "1" }, data: { name: "Karl" }}, input2: {query: { _id: "1" }, payload:...

What's the state of this? What's missing to be merged?

Great question... It's complicated because we're going to follow the [OpenCRUD specs](https://github.com/opencrud/opencrud/) and this case doesn't seem to be handled. I'm going to ask how we should deal with this...

@johannpinson Thank you for sharing the issue on Prisma. I think the OpenCRUD specs could evolve for fixing that kind of issues. I'm not sure that excluding words is the...

I understand but blocking words is not an optimal solution because as a workaround we can add the prefix `all` for these words or change the specs to make sure...

@MartinMuzatko Try to find another word for this model until we find a viable solution.