How to run a mutation? Add example to Readme
See original GitHub issueI can query just fine, but I’m having a hard time figuring out the correct format for mutations. Here’s a screenshot of what I’m playing with:
https://www.dropbox.com/s/4g0r4ii3z3u7zir/Screenshot 2015-12-16 10.58.25.png?dl=0
Basically I’m just not sure of the correct format for setting up the ChangeCohortInput
but I remember seeing someone else do it by making that as a variable in the Query Variables section.
Issue Analytics
- State:
- Created 8 years ago
- Comments:8 (3 by maintainers)
Top Results From Across the Web
spectaql - npm
Supports blacklisting entire areas (e.g. "don't show Mutations") and 1-off blacklisting. Supports providing examples via static metadata, or ...
Read more >/graphql - Lime Go API
Mutations are used to perform certain actions and alter objects. The examples below are quite simple, regarding the request body. In production you'll...
Read more >Documentation for graphql-relay (0.12.0) - RubyDoc.info
To define a mutation, use GraphQL::Relay::Mutation.define . Inside the block, you should configure: name , which will name the mutation field & derived...
Read more >graphql_flutter | Flutter Package - Pub.dev
For more in-depth details on the graphql API, see the graphql README ... In order to use the client, your Query and Mutation...
Read more >aws-cdk/aws-appsync module - AWS Documentation
Example of a GraphQL API with AWS_IAM authorization resolving into a DynamoDb ... To add fields for these mutations, we can simply run...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
If you’re like me, you simply missed the sneaky “variables” input box (bottom left corner):
Let say your
ChangeCohortInput
has the fieldsclientMutationId
andtitle
.Your mutation would look like:
and variables