New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix bug where we cant resolve custom types #6016
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
1 Ignored Deployment
|
No changes to documentation |
Component Testing Report Updated Mar 18, 2024 9:42 AM (UTC)
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice. It's actually very common for us to forget about the type chain too 😅 but I think this will do the trick! 👏
Types inside types inside types is confusing to reason about 😅 rebasing... |
fixes a bug where we cant map custom defined string fields etc
aa20532
to
f2ccf5b
Compare
Description
Found a bug where we some times can't extract a schemaType, turns out we were resolving the wrong schema type.
Types defined like this doesn't work:
What to review
Correctnes
Testing
Added 👍
Notes for release
N/A - no notes needed