fix(http-types-generator, types): correctly generate types for OperatorMap - #15501
Merged
Conversation
🦋 Changeset detectedLatest commit: 59eb780 The changes in this PR will be included in the next version bump. This PR includes changesets to release 78 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
This was referenced Jun 1, 2026
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
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
What — What changes are introduced in this PR?
Correctly generate HTTP types for Zod schemas / properties that use applyAndAndOrOperators
Why — Why are these changes relevant or necessary?
When applyAndAndOrOperators wraps a Zod schema with
z.lazy, TypeScript can't properly resolve the type of the output of the operator map. This leads to properties havinganytype instead of the actual type in the generated type.How — How have these changes been implemented?
Add utilities to walk through an
applyAndAndOrOperatorsand its arguments, looking for a shape that contains some of the common operator map properties like$eq,$ne, etc... and, if found, use theOperatorMaptype for the property.Also fix a property type in the
typespackage that usedanyincorrectly due to this issue.Testing — How have these changes been tested, or how can the reviewer test the feature?
Checklist
Please ensure the following before requesting a review:
yarn changesetand follow the promptsAdditional Context
Add any additional context, related issues, or references that might help the reviewer understand this PR.