POST / PUT / DELETE actions are handled by mutations in GraphQL
there you can also (if you want) only pick your needed result values like:
"add a message, but only return the created ID" (or anything else you need)
Yeah but they just seem way more complex with GraphQL. I would prefer doing "mutations" the RESTful way if I don't need that feature of only returning part of the response. But still keep GraphQL for the GET endpoint.
I think it does mean that the contracts are no so strict and have a dynamic part. Is it?
Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink.
Hide child comments as well
Confirm
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
POST / PUT / DELETE actions are handled by mutations in GraphQL
there you can also (if you want) only pick your needed result values like:
"add a message, but only return the created ID" (or anything else you need)
Yeah but they just seem way more complex with GraphQL. I would prefer doing "mutations" the RESTful way if I don't need that feature of only returning part of the response. But still keep GraphQL for the GET endpoint.
I think it does mean that the contracts are no so strict and have a dynamic part. Is it?