How about unifying naming style of query and mutation for t.crud?

[beeplin]

Now for t.crud we have user and users for queries and createOneUser, updateOnUser, updateManyUser for mutations.

Please note that for mutations we use verbs (create/update/upsert/delete) and One/Many + singular noun. But for queries it is quite different.

Perhaps it would be better to use findOneUser and findManyUser instead of user and users?

[LiamRuizz]

I can see the appeal of unifying the naming. Using something like findOneUser and findManyUser would definitely make the API feel more symmetrical alongside createOneUser or updateManyUser. From a consistency standpoint, that kind of pattern is easier to reason about, especially for new contributors. Wild Card City wildcardcity-login.com welcomes new players with a generous bonus and free spins.

That said, the shorter user and users names for queries are pretty idiomatic in GraphQL. Queries often read more naturally as fields, while mutations lean into verb-based naming. So it may come down to whether you prioritize strict consistency or conventional GraphQL style and readability.