fix: discriminatedUnion allOf issue #249
Merged
Conversation
This file contains 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
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
hey, thank you for working on this ! could you add a a changeset ? |
nmcdaines
force-pushed
the
fix/discriminated-union-issue
branch
from
ed469e2 to
4cadb30
Compare
|
Hey @astahmer, thanks for reviewing and apologies for not including a changeset 🙏 |
Merged
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.
An issue was previously raised #110 whereby the
z.discriminatedUnioncaused issues in the gererated schema.It appears the issue is caused by the
z.andtype, this breaks inference when used within az.discriminatedUnion.In order to solve this, whenever there are multiple objects defined within an
allOfblock we should instead opt to use az.uniontype instead; which then allows thez.andtype to be infered correctly.