Up until now, we have been using a shorthand syntax where we omit both the`query` keyword and the query name, but in production apps it's useful to use these to make our code less ambiguous.

You'll need these optional parts to a GraphQL operation if you want to execute something other than a query or pass dynamic variables.

Up until now, we have been using a shorthand syntax where we omit both the`query` keyword and the query name, but in production apps it's useful to use these to make our code less ambiguous.

Here’s an example that includes the keyword`query` as_operation type_ and`HeroNameAndFriends` as_operation name_ :

}

The_operation type_ is either_query_,_mutation_, or_subscription_ and describes what type of operation you're intending to do.

The_operation type_ is either_query_,_mutation_, or_subscription_ and describes what type of operation you're intending to do. The operation type is required unless you're using the query shorthand syntax, in which case you can't supply a name or variable definitions for your operation.

The_operation name_ is a meaningful and explicit name for your operation. Itcan beveryuseful for debugging and server-side logging reasons.

The_operation name_ is a meaningful and explicit name for your operation. Itis only required in multi-operation documents, but its use is encouraged because it isveryhelpful for debugging and server-side logging.

When something goes wrong either in your network logs or your GraphQL server, it is easier to identify a query in your codebase by name instead of trying to decipher the contents.

Think of this just like a function name in your favorite programming language.

For example, in JavaScript we can easily work only with anonymous functions, but when we give a function a name, it's easier to track it down, debug our code,