RFC-0029 · Design Q&A
Versioned draft snapshot
RFCs, reference catalogs, and evidence reflect Spec 3b2e3e7a114fb826b1445d39a48756b8fff629cd. Counts and pending/status notes belong to that snapshot. Read the dated project update for later progress.
Source repositories are private during staging. Links marked “repository access required” need access to the linked repository.
Q: How does the adapter preserve nullable values separately from absent fields?
Status: Open
Source: RFC-0029 §§4.1, 5; RFC-0024 §6.1
Issue: Zod .optional() and .nullable() both map to an optional field, and TypeScript T | null and T | undefined are both treated as optional. These have distinct wire and validator meanings; collapsing them can make a present null value indistinguishable from an omitted input.
Recommendation: Preserve optionality and nullability as separate properties in the adapter result contract, and map them independently for inputs and outputs.
Q: Which diagnostic reports a flattened operation-name collision?
Status: Open
Source: RFC-0029 §§2, 6, 10 Issue: §6 uses M29901 for two router paths that flatten to the same operation name, but the diagnostic table defines M29901 only as router type not found. Collision and missing-router errors need different actions and source locations. Recommendation: Allocate a separate duplicate-name diagnostic and reject the generated operation set on collision.
Q: What transport contract does a tRPC subscription use?
Status: Open
Source: RFC-0029 §§3, 8.3–8.5; RFC-0020 §§3–8 Issue: The RFC assigns RFC-0020 semantics to a tRPC subscription and says GET is upgraded per RFC-0020, but RFC-0020 explicitly leaves WebSocket and SSE transport unspecified and only defines Gnomon event-log subscriptions. No handshake, framing, cancellation, resume, or credential behavior is supplied for tRPC streams. Recommendation: Define a tRPC transport stream contract and a separate bridge, if needed, for RFC-0020 event-log guarantees.
Q: When may a locked tRPC build skip TypeScript type extraction?
Status: Open
Source: RFC-0029 §9.3; RFC-0024 §6.3 Issue: The adapter must hash the extracted type graph before deciding whether to skip extraction. The lockfile example does not carry a full operation/type snapshot, so it cannot reconstruct a cached result without extraction or prove that transitively imported types are unchanged. Recommendation: Pin the full serialized adapter result and a verified source dependency snapshot; define the offline and invalidation rules through the canonical lockfile contract.