fix(ai): infer Zod outputSchema instead of collapsing to unknown#563
Merged
AlemTuzlak merged 1 commit intoMay 15, 2026
Conversation
Zod's core $ZodType['~standard'] is typed as StandardSchemaV1.Props
(no jsonSchema converter), so chat({ outputSchema: zodSchema }) fell
through to unknown and forced callers to cast or re-parse. Widen
SchemaInput + InferSchemaType to also match StandardSchemaV1 so the
inference recovers; runtime path is unchanged. Add an actionable
runtime error for validator-only schemas (no ~standard.jsonSchema)
that the type widening now lets through.
Closes #562
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Contributor
🚀 Changeset Version Preview1 package(s) bumped directly, 22 bumped as dependents. 🟩 Patch bumps
|
|
View your CI Pipeline Execution ↗ for commit e001048
☁️ Nx Cloud last updated this comment at |
@tanstack/ai
@tanstack/ai-anthropic
@tanstack/ai-client
@tanstack/ai-code-mode
@tanstack/ai-code-mode-skills
@tanstack/ai-devtools-core
@tanstack/ai-elevenlabs
@tanstack/ai-event-client
@tanstack/ai-fal
@tanstack/ai-gemini
@tanstack/ai-grok
@tanstack/ai-groq
@tanstack/ai-isolate-cloudflare
@tanstack/ai-isolate-node
@tanstack/ai-isolate-quickjs
@tanstack/ai-ollama
@tanstack/ai-openai
@tanstack/ai-openrouter
@tanstack/ai-preact
@tanstack/ai-react
@tanstack/ai-react-ui
@tanstack/ai-solid
@tanstack/ai-solid-ui
@tanstack/ai-svelte
@tanstack/ai-utils
@tanstack/ai-vue
@tanstack/ai-vue-ui
@tanstack/openai-base
@tanstack/preact-ai-devtools
@tanstack/react-ai-devtools
@tanstack/solid-ai-devtools
commit: |
AlemTuzlak
approved these changes
May 15, 2026
AlemTuzlak
deleted the
562-chat-inferschematypezzodtypet-resolves-to-unknown-forces-parse-round-trip-or-cast
branch
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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
`chat({ outputSchema: zodSchema })` returned `Promise` (and `StructuredOutputCompleteEvent` resolved with `T = unknown`) because `InferSchemaType` only matched `StandardJSONSchemaV1`. Zod's core `$ZodType['~standard']` is typed as `StandardSchemaV1.Props` — without the `jsonSchema` converter at the type level — so Zod schemas didn't structurally satisfy the JSON-schema branch and fell through to `unknown`, forcing callers to either cast or run a redundant `schema.parse()`.
The Zod type/runtime mismatch
Zod schemas are truly `StandardJSONSchemaV1` at runtime — Zod just hasn't widened the public `~standard` declaration on `$ZodType` to include the `jsonSchema` converter (the `StandardSchemaWithJSONProps` interface exists in their source but isn't applied to `$ZodType`). Looks like an in-progress upstream change.
Approach
`types.ts` — widen `SchemaInput` to also accept `StandardSchemaV1<any, any>`, add a `StandardSchemaV1` branch to `InferSchemaType`. The JSON-schema branch is still tried first (structurally narrower), so callers passing a real `StandardJSONSchemaV1` keep that resolution; Zod (and any future validator-only library) gets the inference via the new branch. `unknown` now means "I have no information," not "Zod was too clever for the matcher."
`schema-converter.ts` — add a runtime guard that throws an actionable error when a Standard Schema validator without `~standard.jsonSchema` is passed. This category was previously rejected at compile time; now that types accept it, the runtime needs to fail loudly instead of shipping `{ '~standard': ... }` straight to the LLM provider.
Runtime path is unchanged for Zod / ArkType / Valibot — `convertSchemaToJsonSchema` still uses the existing `isStandardJSONSchema` structural check, which Zod 4.2+ schemas pass at runtime regardless of their narrow type.
Test plan
InferSchemaType<z.ZodType<T>>resolves tounknown— forces.parse()round trip or cast #562Closes #562
🤖 Generated with Claude Code