Update operation docs #1802
Update operation docs #1802
Conversation
|
@mandiwise is attempting to deploy a commit to the The GraphQL Foundation Team on Vercel. A member of the Team first needs to authorize it. |
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
|
||
| ## Deleting data | ||
|
|
||
| Just as we can send a `DELETE` request to delete a resource with a REST API, we can use mutations to delete some existing data as well by defining another field on the `Mutation` type: |
There was a problem hiding this comment.
I think we should clarify that in GraphQL we send a POST request to delete
There was a problem hiding this comment.
I have an updated "Serving over HTTP" page almost ready to go where I go into this in detail based on the draft GraphQL over HTTP spec (including when GET may be used too). Does it make sense to duplicate that here? My goal was draw connections with REST patterns the reader would likely be familiar with while explaining how different kinds of mutations work without overloading with too much information. It can be tricky to find the right balance though! Let me know what you think.
Co-authored-by: Benjie <[email protected]>
Co-authored-by: Benjie <[email protected]>
Co-authored-by: Benjie <[email protected]>
Co-authored-by: Benjie <[email protected]>
Co-authored-by: Benjie <[email protected]>
Co-authored-by: Dimitri POSTOLOV <[email protected]>
Co-authored-by: Benjie <[email protected]> Co-authored-by: Jonathan Berger <[email protected]>
Co-authored-by: Benjie <[email protected]>
Co-authored-by: Benjie <[email protected]>
Co-authored-by: Benjie <[email protected]>
Co-authored-by: Benjie <[email protected]>
|
Not quite sure what happened here but it went to 136 files changed... I've merged in the latest |
There was a problem hiding this comment.
I like this new structure and this is great content - really really good! I've included some minor nit-picky suggestions below - the only big change I think is that it would be nice to see the purpose-driven mutations content raised to be its own heading so it's easy to link to, and doing so may or may not require some minor reworking of the surrounding text.
src/pages/learn/mutations.mdx
Outdated
| } | ||
| ``` | ||
|
|
||
| As a general rule, schemas should be designed to help clients get the data that they need from the GraphQL API, so the fields defined in a schema should be informed by those use cases. |
There was a problem hiding this comment.
This is really great content, but "get the data that they need from" seems very query-focussed (and side-effect free) - can you tweak it so that it better reflects mutations?
There was a problem hiding this comment.
Fixed in 1f3ae06.
Co-authored-by: Benjie <[email protected]>
Addresses #250, #584, #728, #754, and #992
Description
This PR contains updated operations-related content in the Learn docs. Key changes include:
@benjie @jorydotcom