GraphQL Conformance
Lanexio™ Parser implements GraphQL parsing with auto-detection of executable documents versus SDL (Schema Definition Language). The conformance suite validates both modes plus malformed-input rejection.
Test results
Section titled “Test results”205 tests pass, 7 skipped. The skipped tests are documented non-blocking gaps — the parser is lenient rather than strict, accepting input a validator would reject. Each skip carries an inline rationale. Lenient parsing is the design choice: parse what you can, flag what you can’t, never throw.
Corrected gate: every returned tree carries metadata.language === "graphql" (stamped on both the main and the never-throw catch path), and the exhaustive harness reports 9,096 / 9,096 results passing (100.00%) on the corrected gate (1,516 test_files/graphql files x 6 modes). Invalid-UTF-8 bytes (e.g. 0xff) are surfaced as GraphqlKind.Error leaves in the main dispatch loop and inside directive arguments (including object and list values) rather than silently skipped, so emitSource(parse(x)) === x holds byte-for-byte even on malformed input.
Auto-detection
Section titled “Auto-detection”parseGraphql inspects the input and routes to the executable-document parser or the SDL parser automatically. Callers don’t need to specify which mode to use.
Four-axis bar
Section titled “Four-axis bar”| Axis | Result |
|---|---|
| never-throw | 0 throws across full corpus |
| well-formed | corpus WF = 0 |
| lossless | corpus lossless = 0, byte-exact round-trip (corrected gate; invalid-UTF-8 bytes emit Error leaves in the main loop and in directive arguments instead of opening a gap) |
| conformance | 205 passing, 7 documented skips |
Corpus conformance
Section titled “Corpus conformance”pnpm conformance:suite measured this family over the test_files/graphql corpus on 2026-10-06
at Lanexio™ Parser version 1.0.0:
| family | valid | invalid | raw | contract-subset | REAL-DEFECT |
|---|---|---|---|---|---|
| graphql | 1510 | 6 | 99.7% | 99.9% (1508/1510) | 2 |
The contract-subset here is the clean valid inputs over all valid inputs (this family carries no artifact buckets); the 2 REAL-DEFECT entries are valid-classified files that report an error.