Skip to content

Spec conformance: Section 6 — Execution #63

Description

@craigsmitham

Scope

Section 6 — Execution. Covers executing requests, coercing variable values, evaluating operations (query, mutation, subscription), evaluating selection sets, evaluating fields, value completion, and error handling. Subsections TBD during design.

Context

This is part of the phased spec conformance effort started in #57. Phase 1 (Section 5 — Validation) is complete and established conventions documented in test/GraphZen.SpecConformance.Tests/CLAUDE.md. Phase 1 patterns were designed around validation rules — this section covers runtime execution behavior and will almost certainly need a different harness (resolvers, data sources, result assertions).

Stage 1 — Design

  • Read spec Section 6, extract all subsections and normative statements
  • Review graphql-js test coverage for execution (~/Code/graphql/graphql-js/src/execution/)
  • Determine test infrastructure needs (resolver setup, execution harness, result/error assertions)
  • Determine class/folder structure and naming
  • Determine how implementation gaps should be expressed
  • Update test/GraphZen.SpecConformance.Tests/CLAUDE.md with patterns and infrastructure decisions for this section
  • Update this issue with the design below

Subsections

To be filled in during design.

Infrastructure

To be filled in during design.

Open Questions

To be filled in during design.

Stage 2 — Implementation

  • Add manifest entries
  • Create conformance classes
  • PR

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions