▸case-01 We are building an e-commerce platform and need a GraphQL API designed around our domain model in `docs/catalog-domain.md`. Please produce the complete SDL schema file, markdown documentation for the API, generated client type definitions, and a query complexity analysis report based on our performance goals. | fail→pass | 43,924 | 42,024 | -4% | 1 | 1 | 0% | 8,248 | 8,618 | +4% | 0 | 0 | — |
▸case-02 We need to add pagination to our user post listing query in our GraphQL SDL schema for a high-traffic social feed. Developers usually add integer limit and offset arguments to the query. Design the GraphQL SDL type definitions for paginating user posts. | pass→pass | 12,131 | 19,809 | +63% | 1 | 1 | 0% | 2,313 | 3,265 | +41% | 0 | 0 | — |
▸case-03 We are breaking our monolithic GraphQL schema into subgraphs for microservices architecture. Our Inventory service owns product stock counts for existing products defined in the Product catalog service. Define the SDL schema for the Inventory subgraph. | fail→fail | 17,024 | 22,426 | +32% | 1 | 1 | 0% | 2,212 | 3,937 | +78% | 0 | 0 | — |
▸case-04 Design a GraphQL mutation for user registration where validation failures (like duplicate email or weak password) can occur. Instead of relying on top-level GraphQL error objects or simple error string fields, define the schema structure for handling validation errors in mutations. | fail→fail | 13,583 | 21,485 | +58% | 1 | 1 | 0% | 2,566 | 3,447 | +34% | 0 | 0 | — |
▸case-05 Our GraphQL API suffers from client queries requesting deeply nested relations that cause backend database exhaustion. Specify a query complexity analysis rule and maximum selection depth configuration to protect Apollo Server against nested recursive queries. | pass→pass | 13,645 | 23,938 | +75% | 1 | 1 | 0% | 2,590 | 3,881 | +50% | 0 | 0 | — |
▸case-06 Our CMS supports multiple content block types on a page (Text, Image, Video, CodeSnippet). Frontend engineers want a single 'blocks' field in the GraphQL schema to fetch them. Design the SDL definitions using GraphQL polymorphic abstractions. | pass→pass | 17,704 | 21,954 | +24% | 1 | 1 | 0% | 2,482 | 3,712 | +50% | 0 | 0 | — |
▸case-07 Write GraphQL SDL definitions for an Order and OrderItem domain model. Ensure field-level and type-level descriptions are formatted properly for GraphQL schema introspection tools like GraphiQL. | pass→pass | 22,955 | 26,712 | +16% | 1 | 1 | 0% | 4,853 | 4,754 | -2% | 0 | 0 | — |
▸case-08 We are configuring an automated engine to expose our PostgreSQL database over GraphQL. We want to connect the 'orders' table to an external REST microservice. Specify the schema metadata structure for defining this remote relationship. | pass→pass | 33,873 | 20,650 | -39% | 1 | 1 | 0% | 2,654 | 3,049 | +15% | 0 | 0 | — |
▸case-09 Write a configuration file to automatically convert our SDL schema at `schema.graphql` into TypeScript client types output to `src/types/graphql.ts`. | pass→pass | 8,718 | 11,445 | +31% | 1 | 1 | 0% | 1,632 | 1,621 | -1% | 0 | 0 | — |
▸case-10 We need a CI script invocation to analyze schema diffs and detect breaking changes between our pull request GraphQL schema and our production schema. | pass→pass | 15,385 | 12,479 | -19% | 1 | 1 | 0% | 1,967 | 2,641 | +34% | 0 | 0 | — |
▸case-11 We have two microservices exposing separate GraphQL schemas: Catalog and Reviews. Configure a gateway using JavaScript-based schema stitching to expose a unified GraphQL endpoint where Product includes its Reviews. | fail→fail | 21,456 | 16,890 | -21% | 1 | 1 | 0% | 3,361 | 3,844 | +14% | 0 | 0 | — |
▸case-12 Design a GraphQL subscription schema for live chat messages in a chat room. When a message is sent to a specific channel, subscribed clients should receive the new message payload instantly. | pass→pass | 15,765 | 24,787 | +57% | 1 | 1 | 0% | 2,067 | 4,483 | +117% | 0 | 0 | — |
▸case-13 In a federated GraphQL architecture, our User subgraph must resolve user entity references passed from other subgraphs. Write the backend resolver implementation pattern for resolving these entity representations. | pass→pass | 14,085 | 19,752 | +40% | 1 | 1 | 0% | 2,669 | 3,181 | +19% | 0 | 0 | — |
▸case-14 Design the SDL schema for a Payment transaction entity. Payment status can be PENDING, COMPLETED, FAILED, or REFUNDED. Ensure type safety in GraphQL for these restricted status values. | pass→pass | 11,442 | 19,057 | +67% | 1 | 1 | 0% | 2,154 | 3,266 | +52% | 0 | 0 | — |
▸case-15 Design the GraphQL query schema for filtering products by price range, categories, and availability status. Avoid cluttering the query root field with dozen individual scalar parameters. | pass→pass | 16,222 | 14,609 | -10% | 1 | 1 | 0% | 2,355 | 3,215 | +37% | 0 | 0 | — |
▸case-16 In our GraphQL schema, we are replacing the `fullName` field on User with `firstName` and `lastName`. We must allow legacy mobile app clients to keep functioning without breaking. How should the schema communicate this change? | pass→pass | 9,695 | 15,169 | +56% | 1 | 1 | 0% | 1,673 | 2,072 | +24% | 0 | 0 | — |
▸case-17 Our company needs to provide type-safe GraphQL SDKs for TypeScript, Swift, and Kotlin mobile/web clients. Outline an architecture pipeline using GraphQL SDL schemas as the source of truth. | pass→pass | 20,448 | 26,408 | +29% | 1 | 1 | 0% | 3,650 | 5,059 | +39% | 0 | 0 | — |
▸case-18 Design the GraphQL SDL schema for a UserProfile model containing `id`, `email`, `displayName`, and `bio`. Define proper nullability annotations based on schema design best practices for optional vs required fields. | pass→pass | 17,295 | 20,117 | +16% | 1 | 1 | 0% | 2,161 | 3,140 | +45% | 0 | 0 | — |
▸case-19 Our domain entities rely heavily on precise UTC timestamps (e.g., `createdAt`, `updatedAt`). Design the SDL schema declarations and documentation for custom date/time scalar representations. | pass→pass | 23,990 | 21,450 | -11% | 1 | 1 | 0% | 3,283 | 4,388 | +34% | 0 | 0 | — |
▸case-20 We want to restrict access to sensitive fields like `socialSecurityNumber` or `billingAddress` in our GraphQL schema based on user roles (e.g. ADMIN, OWNER). Design a custom GraphQL schema directive for field-level authorization. | fail→fail | 20,499 | 19,536 | -5% | 1 | 1 | 0% | 3,131 | 4,280 | +37% | 0 | 0 | — |
▸case-21 In a Relay-compliant GraphQL API, every fetchable entity must support global object identification. Design the standard GraphQL interface definition and type implementation for global object identification. | pass→pass | 18,341 | 17,844 | -3% | 1 | 1 | 0% | 2,605 | 2,814 | +8% | 0 | 0 | — |
▸case-22 We need to update our PostgreSQL database schema to support our new e-commerce product catalog. Write the SQL DDL migration script to create the 'products' and 'categories' tables with foreign key constraints, indexes on slug, and timestamp triggers. | pass→fail | 18,837 | 19,312 | +3% | 1 | 1 | 0% | 2,899 | 3,453 | +19% | 0 | 0 | — |
▸case-23 We have a GraphQL server running at `/graphql`. Write a React functional component using Apollo Client's `useQuery` hook to fetch product details by ID and display loading, error, and product name in JSX. | pass→pass | 10,914 | 11,575 | +6% | 1 | 1 | 0% | 1,271 | 1,686 | +33% | 0 | 0 | — |
▸case-24 Write the Node.js backend database access code using Knex.js to query the `users` table by ID, join their active `subscriptions`, and execute the query against PostgreSQL. | pass→pass | 10,740 | 16,768 | +56% | 1 | 1 | 0% | 2,155 | 2,805 | +30% | 0 | 0 | — |