All 15 GraphQL questions
More in GraphQL
What is GraphQL, and how does it differ from a traditional REST API in terms of how clients request data? How would you set up a basic GraphQL server in Node.js using Apollo Server, defining a schema and resolvers? What is the difference between a GraphQL Query, Mutation, and Subscription operation type? What is GraphQL introspection, and why might you want to disable it in a production environment? What is the purpose of GraphQL fragments, and how do they help avoid duplicating field selections across multiple queries? How would you handle file uploads in a GraphQL API, given GraphQL's standard JSON-based transport doesn't naturally support binary file data? What is the purpose of GraphQL's non-null (!) type modifier, and what happens if a resolver for a non-null field returns null unexpectedly? What is the difference between a GraphQL scalar type and an object type, and how would you define a custom scalar (like DateTime) in a Node.js GraphQL server? What is the N+1 query problem in GraphQL specifically, and how does DataLoader solve it? How would you implement authentication and authorization in a GraphQL API in Node.js, given there's typically only a single HTTP endpoint?
Advertisement
Node.js › GraphQL

What is the difference between a GraphQL query variable and hardcoding a value directly inside the query string?

Beginner

Answer

Query variables let you parameterize a GraphQL query with dynamic values passed separately from the query document itself (similar in spirit to a parameterized SQL query), rather than string-interpolating values directly into the query text -- this makes queries reusable across different inputs without needing to construct a new query string each time, and importantly avoids a class of injection-like bugs that could arise from improperly escaping interpolated values directly into the query syntax.
# Using a variable, defined separately from the query string
query GetUser($userId: ID!) {
  user(id: $userId) { name, email }
}

// Sent alongside the query as a separate variables object
{ "userId": "123" }
Real-world example A frontend application defines a single parameterized GetUser query once and reuses it for every different user ID needed throughout the app, simply passing a different variables object each time rather than constructing a brand new query string with the ID interpolated directly for every single request.

Common follow-ups: Why is directly interpolating a value into a GraphQL query string considered a worse practice than using variables, beyond just convenience?;How do query variables interact with GraphQL client libraries' caching mechanisms, like Apollo Client's normalized cache?

Security;RESTful API Design with Express
All 15 GraphQL questions