jprdonnelly/docs
1
0
Fork 0
mirror of synced 2025-12-23 21:07:12 -05:00
Code Issues Projects Releases Wiki Activity

Fix list Markdown formatting

Browse Source
This commit is contained in:
Vladimir Rutsky
2020-10-25 18:07:33 +01:00
committed by GitHub
parent 0d0e351853
commit 533c532fc1
1 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
content/graphql/guides/forming-calls-with-graphql.md
View File

@@ -334,9 +334,9 @@ With the ID known, we can proceed with the mutation:
Let's examine this line:
- `addReaction` is the name of the mutation.
- `input` is the required argument key. This will always be `input` for a mutation.
- `{subjectId:"MDU6SXNzdWUyMzEzOTE1NTE=",content:HOORAY}` is the required argument value. This will always be an [input object](/v4/input_object/) (hence the curly braces) composed of input fields (`subjectId` and `content` in this case) for a mutation.
- `addReaction` is the name of the mutation.
- `input` is the required argument key. This will always be `input` for a mutation.
- `{subjectId:"MDU6SXNzdWUyMzEzOTE1NTE=",content:HOORAY}` is the required argument value. This will always be an [input object](/v4/input_object/) (hence the curly braces) composed of input fields (`subjectId` and `content` in this case) for a mutation.
How do we know which value to use for the content? The [`addReaction` docs](/v4/mutation/addreaction/) tell us the `content` field has the type [`ReactionContent`](/v4/enum/reactioncontent/), which is an [enum](/v4/enum) because only certain emoji reactions are supported on GitHub issues. These are the allowed values for reactions (note some values differ from their corresponding emoji names):