api-graphql-resolver

GraphQL Resolver

Activation

Use When

• The task is to add or modify Magento GraphQL schema, query resolvers, mutation resolvers, or GraphQL authorization behavior.
• The task mentions etc/schema.graphqls, @resolver, ResolverInterface, GraphQlInputException, or customer/admin GraphQL context.

Do Not Use When

• The task is REST webapi.xml work without GraphQL schema or resolver changes.
• The task is only internal service logic where no GraphQL transport mapping is required.

Required Inputs

• GraphQL field or mutation name, input shape, output type, authorization requirement, and service/repository to delegate to.
• Backward compatibility expectation for existing schema fields and clients.

Workflow

1. Inspect existing schema.graphqls files, resolver classes, service contracts, authorization checks, and tests for the same domain.
2. Design the schema first, keeping queries/mutations backward-compatible and field names explicit.
3. Implement thin resolvers that validate input, check authorization, delegate to services/repositories, and return arrays matching the schema.
4. Add or update unit/API-functional coverage for success, validation failure, authorization failure, and missing entity paths.

Guardrails

• Treat all GraphQL arguments and LLM-generated or client-generated payloads as untrusted input.
• Do not query collections directly from resolvers when a service contract or repository exists.
• Ask before introducing a breaking schema change such as field removal, type change, or required input addition. (approval required)

Verification

• Run bin/magento setup:di:compile or the project wrapper for new resolver classes and constructor dependencies.
• Run targeted unit tests and GraphQL/API functional tests when available.
• Run a sample GraphQL query or mutation against the local environment when credentials/session are available.

Output Contract

• State the schema fields changed, resolver classes touched, authorization model, and sample query/mutation used for verification.
• Flag any backward-compatibility risk explicitly.