Windsurf vs GitHub Copilot

Build a TypeScript GraphQL API with Apollo Server backed by {{database}}. Schema: a {{resource}} type, a query for one {{resource}} by id, a cursor-paginated list query, and create, update, delete mutations returning a payload with a userErrors field instead of throwing. Put SDL in src/schema.graphql, resolvers under src/resolvers/, and a dataloader per relation to prevent N+1 lookups. Validate input at the resolver boundary and map {{database}} failures to typed errors. Ask before installing packages. Then start the server from the Windsurf terminal and run an introspection query plus one create-then-fetch round trip to prove the wiring. Finish by listing every file you created and the nullability decisions you made so I can review them.

Create a GraphQL API for a book catalog in {{language}}, schema first. Start in schema.graphql: types Book, Author, and Review, a books query with cursor pagination taking first and after, and an addReview mutation returning the updated Book. Then open src/resolvers/ and write one resolver file per type, reading from {{database}} through the existing db module, no raw connection strings. Wire a DataLoader for Author so resolving fifty books issues one author query, not fifty. Mutations must validate that rating sits between 1 and 5 and return a typed error in the payload rather than throwing. Reference #file:schema.graphql in follow-ups so the chat stays anchored to the contract. To verify, I will start the server and run a query fetching ten books with authors while logging SQL, expecting two statements.

Audit this repo for missing error handling and fix it in layers. Start with a Cascade search for bare awaits, empty catch blocks, and promise chains without rejection paths; group findings by file and show me before editing. Then add a shared asyncHandler around route handlers, one error middleware mapping known error types to status codes and hiding stack traces outside development, and a timeout plus typed failure result on every external call: network, filesystem, {{database}}. On the UI side, wrap the route tree in an error boundary with a retry action. Every fix ships with a test that forces the failure: reject the promise, sever the connection, throw inside a child component. Run the suite from the Windsurf terminal and report each forced-failure test you added.

Audit src/services/ for swallowed and unhandled errors, then fix and prove each fix with a test. Hunt for four patterns: awaited calls with no try around them in request handlers, catch blocks that only console.log, fetch responses used without checking res.ok, and JSON.parse on external input. Replace them with a small error hierarchy in src/errors.ts, AppError with an HTTP status and a code, plus NotFoundError and UpstreamError subclasses, and one boundary in the request pipeline that maps AppError to a response and everything else to a logged 500 with no stack in the body. Every fix gets a companion test in the matching .test file that forces the failure, a 404 from an upstream stub, malformed JSON, a rejected promise, and asserts the mapped status and code. Print a table of file, pattern found, fix applied. I will verify by reverting one fix locally and watching its companion test fail.