What problem does it solve?
Extending a Webiny project's GraphQL API with custom queries, mutations, and business logic requires knowing the correct factory pattern, DI conventions, and registration steps—mistakes like missing file extensions or wrong export styles cause build failures.
Core Features & Use Cases
- Custom Queries and Mutations: Implement
GraphQLSchemaFactory.Interface to add type definitions and resolvers via the schema builder.
- Per-Resolver Dependency Injection: Inject request-scoped services like identity, tenancy, and CMS use-cases directly into resolvers.
- Namespaced Schemas and Dynamic Inputs: Build namespaced mutation patterns and generate GraphQL input fields dynamically from CMS models.
- Use Case: You need a
whoAmI endpoint or a createEntity mutation backed by a UseCase—this Skill provides the full pattern from schema definition to <Api.Extension> registration and deployment.
Quick Start
Add a custom GraphQL query to my Webiny API that returns the current user's identity using GraphQLSchemaFactory.