-
Notifications
You must be signed in to change notification settings - Fork 223
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
Is there a maintained fork of ozzo-validation? #162
Comments
Would like to know too |
I'd also like to know! This is the only validation library that I've actually enjoyed using |
Also would like too know! |
I've made a fork of this project and I'm planning to maintain it, any help it's welcome. For the moment I only upgrade the Go version to v1.18 |
We have an actively maintained fork as well. It has a few additions and fixes, most of which are from the PRs found in this repository. |
How is perfomance compared to https://github.com/go-playground/validator ? |
@ysomad The core functionality of that fork is the same as ozzo-validation's, which means the performance is also the same. I haven't compared this with https://github.com/go-playground/validator but I also don't see any reason to do that either as both libraries are using the reflection package under the hood. |
I'm using https://github.com/gookit/validate which is also good. Not sure about performance though. |
Seems like this library is no longer maintained. Is there an actively maintained fork out there?
Thank you!
The text was updated successfully, but these errors were encountered: