feat: add library-based ts-to-zod schema generation #1292
+7,872
−15
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Add auto-generated Zod schemas and types from
spec.types.tsusing ts-to-zod, with pre-processing to match SDK type hierarchy.Pipeline
Pre-Processing (NEW)
Instead of post-processing generated schemas, we now pre-process the types:
This transforms the type hierarchy so generated types/schemas match SDK conventions, where
jsonrpc/idfields are handled at the transport layer.Generated Files
sdk.types.ts- Pre-processed types (SDK hierarchy)sdk.schemas.ts- Zod schemas from sdk.types.tssdk.schemas.zod.test.ts- Integration testsindex.ts- Public API with explicit exportsPost-Processing
"zod"→"zod/v4"z.record().and(z.object())→z.looseObject()jsonrpc: z.any()→z.literal("2.0")ProgressTokenSchema,RequestIdSchemause.int()Usage
What's Next
With
sdk.types.tsnow generated,types.tscan become a thin re-export layer:Test plan
npm run generate:schemasproduces sdk.types.ts + sdk.schemas.tsnpm run buildsucceeds🤖 Generated with Claude Code