Learning about directives

While it’s not mandatory to use GraphQL directives, they can be incredibly useful in many cases. Directives provide a way to add additional instructions or metadata to our GraphQL schema and queries, allowing us to modify the behavior or control the execution of certain fields or operations.

Handling authentication

One common use case for directives is to handle authentication and authorization. For example, by implementing and applying a directive such as @auth or @hasRole to specific fields or types, we can easily enforce access control rules. This ensures that only authenticated users or users with certain roles can access sensitive data or perform certain operations.

In the following example, you will see how to use directives inside the schema to prevent unauthorized access to the resolver:

type User {
  id: ID!
  name: String!
  email: String!
  role: Role!
}
enum Role {
  ADMIN
 ...