Sacha Greif
Sacha Greif
I've heard from some people that "GraphQL Rules" as a name can feel a bit too strict and rigid, and I fear some people might be unwilling to contribute because...
In any mutation you will need to A) identify the document/row/item to mutate and B) pass the mutated data. Sometimes these can both be done with a single argument (pass...
I don't know how easy it would be to do this in practice, but I think it could be very cool to list who uses the different patterns. For example:...
Currently mutations look like: ``` updateUser(where: { id: "1" }, data: { name: "Karl" }) ``` This goes against the guidelines outlined here: > Mutations should only ever have one...
It'd be nice to show an example for the UserOrderByInput type.
https://gist.github.com/swalkinshaw/3a33e2d292b60e68fcebe12b62bbb3e2
skip/after/before/first/last don't seem to be documented anywhere?
OpenCRUD currently uses the word "multi" to designate queries that return multiple documents (as opposed to "single"). Currently, in Vulcan we use the word "list". I think "multi" is better...
Not sure if there's a link to this repo anywhere in the document?
The document mentions an `@relation` directive but then never uses or explains it?