fix: Zod to JSONSchema pipe strategies #962
Open
+2
−1
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.
When converting Zod schema to JSONSchema, set the pipe strategy to the mode corresponding to the schema being generated, either input or output.
This should help fix issues when the Zod schema has transforms.
Motivation and Context
Some Zod schemas have transforms in the form of pipes.
When generating a JSONSchema,
zod-to-json-schema
needs to be instructed as to which "side" of the pipe it should select for the JSON schema. For examplez.string().pipe(z.number())
will be a string as input but number as output.How Has This Been Tested?
I've been applying this
patch-package
for a few weeks in production.Breaking Changes
Types of changes
Checklist
Additional context