GraphQL - Basics and Philosophy
You want to add a new mutation to update a user's email in a schema-first GraphQL API. Which schema definition correctly adds this mutation?
You want to add a new mutation to update a user's email in a schema-first GraphQL API. Which schema definition correctly adds this mutation?
hard📝 schema Q15 of 15
Step-by-Step Solution
Solution:
Step 1: Recall mutation syntax in schema-first SDL
Mutations are defined inside a 'type Mutation { ... }' block with fields representing mutation functions and their arguments and return types.Step 2: Analyze each option
type Mutation { updateUserEmail(id: ID!, email: String!): User } correctly defines a mutation field with required id and email arguments and returns a User type. mutation updateUserEmail(id: ID!, email: String!): User uses incorrect syntax without 'type'. type Mutation updateUserEmail(id: ID!, email: String!): User misses braces. type Mutation { updateUserEmail(id: ID, email: String): Boolean } uses optional args and returns Boolean, which may not match update use case.Final Answer:
type Mutation { updateUserEmail(id: ID!, email: String!): User } -> Option AQuick Check:
Mutations inside 'type Mutation { }' with args and return type [OK]
Quick Trick: Mutations go inside 'type Mutation { }' with args and return type [OK]
Common Mistakes:
- Omitting 'type' keyword for Mutation
- Forgetting braces around Mutation fields
- Using optional args when required
- Returning wrong type for update mutation
Master "Basics and Philosophy" in GraphQL
Want More Practice?
15+ quiz questions · All difficulty levels · Free
Free Signup - Practice All QuestionsMore GraphQL Quizzes