|
|
|
|
|
|
by Humphrey
909 days ago
|
|
|
The author has almost perfectly described the pattern behind GraphQL mutations! That is, a command on the server that represents a user action, takes input, and returns the updated data that has changed. While many people dislike the whole GraphQL stack (I love it, it solves all the problems the author has with REST), I think we can all agree with the usefullness of the pattern that mutations are built upon. |
|
|