-
-
Notifications
You must be signed in to change notification settings - Fork 149
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(types): types result with schema as any #570
Conversation
I'd rather we keep the previous behavior and just return |
We totally can. Just to make sure what you say "keep the previous behavior" you mean the "new previous one" ? 😅 Because what I reproduced here was based on the results were with an So we can decide to change this in favor of "everything is any" but it'll probably be considered as a breaking change by the users so maybe we wanna warn them somehow, or make it clear in the release that this was undesired behavior before. |
Ahh ok got it - yeah let's preserve this behavior then 👍 |
🎉 This PR is included in version 1.17.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
What kind of change does this PR introduce?
Fixes the regression in the types inferences if the client is called without a valid schema and defaulted to any
Context: https://discord.com/channels/839993398554656828/1300816893682126912/1301172995326476288
What is the current behavior?
Please link any relevant issues here.
What is the new behavior?
Feel free to include screenshots if it includes visual changes.
Additional context
Add any other context or screenshots.