Skip to content
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

refactor: use Zod as the default validation library #144

Merged
merged 3 commits into from
May 27, 2024
Merged

Conversation

TheEdoRan
Copy link
Owner

TypeSchema supports multiple validation libraries, but it can cause some issues with Vercel deployments and edge runtime. This commit moves the support for multiple validation libraries to /typeschema path, and root path now requires Zod as validation library.

Related issue(s) or discussion(s)

…ema` import

TypeSchema supports multiple validation libraries, but it can cause some issues with Vercel
deployments. This commit moves the support for multiple validation libraries to `/typeschema` path,
and root path now requires Zod as validation library.
Copy link

vercel bot commented May 27, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
next-safe-action-playground ✅ Ready (Inspect) Visit Preview 💬 Add feedback May 27, 2024 4:55pm
next-safe-action-website ✅ Ready (Inspect) Visit Preview 💬 Add feedback May 27, 2024 4:55pm

Copy link

🎉 This PR is included in version 7.0.0-next.45 🎉

The release is available on:

Your semantic-release bot 📦🚀

Copy link

🎉 This PR is included in version 7.0.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[INTERNAL] [v7] Use Zod as the default validation library
1 participant