-
-
Notifications
You must be signed in to change notification settings - Fork 35
[Feature Request] Standard Schema #528
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
Comments
I believe it is possible, but finding the right balance between flexibility and simplicity is challenging. We need to ensure that we have a good API and comprehensive documentation to support it. Supporting a standard schema is a breaking change. |
Use every StandardSchema compliant library for validation. Closes: #528
@thejackshelton I created a first working version, but I really need help testing the new syntax and ensuring that the old one does not break. |
Hey Sebastian, this is awesome! Once I get the MDX integration for Qwik and content collections in a good enough state I have more bandwidth to test. I've been in the process of porting mdx-bundler, as there is no way to integrate with vite based tools in reality, and the current maintenance of the package does not intend to support agnostic tools (despite the readme). |
Use every StandardSchema compliant library for validation. Closes: #528
Explain the use of Standard Schema in the configuration. Add a page that describes the migration process.
https://github.com/standard-schema/standard-schema
would it be possible to implement standard schema and support different projects like valibot or arktype?
The text was updated successfully, but these errors were encountered: