A REST-shaped workflow
MULTIPLE REQUESTSEach endpoint defines its own response, even when you only need a couple of fields.
What if one request could return a support case, its customer, assigned engineer, and event history—without another endpoint? CaseGraph lets you find out by writing and running real GraphQL.
query GetCase { case(id: "1") { subject severity customer { name plan } assignee { name } } }
REST often needs multiple trips to collect related records. GraphQL lets the client describe its required shape, while the server validates the request against a typed schema.
Each endpoint defines its own response, even when you only need a couple of fields.
query { case(id: "1") { subject customer { name } assignee { name } events(first: 2) { message } } }
Fetch connected records in one operation, selecting only the fields your UI needs.
A contract defining available types, fields, arguments, and their relationships.
A read operation that specifies exactly which fields to return.
A write operation for creating or changing data. Public writes are intentionally blocked in this demo.
Server-side logic that fulfills each field, linking cases to customers and engineers.
Real GraphQL, real validation, real responses. Change the fields, run the query, and see what comes back from the server.
POST /graphql{
"message": "Run a query to inspect the response."
}One operation returns case details and linked customer, assignee, and event data. Remove fields to see how the response changes.
/graphql. Fictional support data only. Protected mutation examples are provided to teach authorization errors; changes cannot be saved to this public demo. Run the persistent local version ↗Four primary object types and a typed schema make the relationships discoverable. GraphQL clients can inspect this contract using introspection.
CASEGRAPH / SAMPLE SCHEMA RELATIONSHIPS
type SupportCase { id: ID! subject: String! status: CaseStatus! severity: Severity! customer: Customer! assignee: Agent events(first: Int): [CaseEvent!]! } type Query { case(id: ID!): SupportCase cases(first: Int, after: String): CaseConnection! metrics: CaseMetrics! }
GraphQL isn't just about successful queries. Learn how a support engineer distinguishes syntax problems, schema mismatches, authorization failures, and expected empty results.
CaseGraph includes a TypeScript server, schema and resolvers, SQLite persistence for local use, typed operations, and tests. Explore the code to see how each layer fits together.
$ git clone https://github.com/ devin-thomas/graphql-test.git $ cd graphql-test $ npm install $ npm start ✓ localhost:4000 ✓ /graphql ready