feat: add create graphql mutation #61
Conversation
Signed-off-by: Brent Hoover <[email protected]>
Signed-off-by: Alvaro Bueno <[email protected]>
Signed-off-by: Alvaro Bueno <[email protected]>
brent-hoover
changed the title
Signed-off-by: Brent Hoover <[email protected]>
Signed-off-by: Brent Hoover <[email protected]>
Signed-off-by: Brent Hoover <[email protected]>
brent-hoover
dismissed
MohanNarayana’s stale review
Rewrite to fit guide format
|
|
||
| ## What you need | ||
|
|
||
| You need to understand what key you will use to query the data, and what the payload of the data is. |
There was a problem hiding this comment.
We don't have it yet, but are the going to be inlinks into our GraphQL documentation or out to 3rd party GraphQL docs if they need more info on these two items?
|
|
||
| ## Define the mutation in the schema | ||
|
|
||
| - If it doesn't already exist, create `schemas` folder in the plugin, and add an `index.js` file there. |
There was a problem hiding this comment.
Similar comment to the other. I would drop the bullets and try to consolidate a little, like:
If it doesn't already exist, create schemas folder in the plugin and add an index.js file there. Then check to see if there is a schema.graphql file in your schemas directory within the plugin. If there isn't, create that file now.
Import the GraphQL file...
|
|
||
| > NOTE: For large plugins, you can split to multiple `.graphql` files and export a multi-item array. | ||
|
|
||
| - In the `.graphql` file, add your mutation within `extend type Mutation { }`. Add an `extend type Mutation` section near the top if the file doesn't have it yet. |
There was a problem hiding this comment.
Suggest to drop bullets on this one and the 4 items below this to stay in line with what I'm seeing live on /Developer
|
|
||
| ## Create the plugin mutation file | ||
|
|
||
| - If it doesn't already exist, create `mutations` folder in the plugin, and add an `index.js` file there. |
There was a problem hiding this comment.
Suggest dropping bullets from this lines as well. Seems to me that a step under a heading doesn't need bullets, whereas a step that has multiple sub-steps or things you need to consider within that step may benefit from bullets.
Signed-off-by: Brent Hoover [email protected]