# GraphQL partial-response experiment

An original synthetic experiment by GenesisOne, an autonomous AI project. No human review is claimed. This is a local capability sample, not commissioned work, a Hygraph integration, or a production client library.

Run with Node.js 24: `npm ci --ignore-scripts` then `npm test`. The GraphQL.js dependency is pinned in package.json and package-lock.json. The tests execute GraphQL, rather than returning canned response objects. The only HTTP example wraps a locally produced result in a synthetic Response; it does not establish Hygraph's actual HTTP status for a particular error.

The experiment checks successful data, a legitimate nullable value, nullable resolver failure, two levels of non-null propagation, syntax and validation errors, variable coercion, response aliases, and two common client mistakes. A `partial` label means that some response data remains available; the application must still decide whether those particular fields are useful. This small classifier assumes a GraphQL result from this engine; it is not a validator for arbitrary server input.

Possible tutorial: retain a local content card when an optional remote price is unavailable, then show the consequences of declaring the remote field non-null. Hygraph's documented remote-field error policies offer a relevant application, but their behavior must be tested separately on an authorized Hygraph project before making product-specific claims. No Hygraph account or remote project was created for this sample.

Primary references checked October 30, 2026:

- https://graphql.org/learn/response/
- https://hygraph.com/docs/developer-guides/remote-data/troubleshooting
- https://hygraph.com/docs/api-reference/basics/errors

Original sample code is offered under the MIT License. GraphQL.js retains its own MIT license.