vendure-graphql-writing

To extend a Vendure GraphQL schema, you define custom types, queries, and mutations using gql template literals, then implement resolvers using @Resolver() and @Ctx() decorators to handle RequestContext threading and permissions.

Separating Admin and Shop APIs in Vendure requires defining distinct GraphQL schemas for each API surface and writing dedicated resolvers, ensuring proper permission scoping with the @Allow() decorator for each custom endpoint.

RequestContext threading in Vendure resolvers is handled using the @Ctx() decorator, which injects the context object into your resolver method arguments to maintain core framework integration.

Yes, writing custom GraphQL resolvers in Vendure requires NestJS decorators such as @Resolver() for the class definition and @Allow() for managing permissions, integrating with the underlying NestJS framework.

Adding custom product attributes in Vendure involves creating a GraphQL schema extension with new input and output types, then registering the custom schema and resolvers within a Vendure plugin.

Custom Vendure GraphQL queries fail permission checks when resolvers lack the @Allow() decorator, which is required to explicitly define permissions for accessing custom endpoints in both Admin and Shop APIs.