You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Given the lack of updates and bug fixes in the last two years, I've taken the liberty of creating a new independent fork. We're open to Issues and Pull Requests at https://github.com/invopop/validation.
We first looked at a few of the other forks, but decided that the base version of ozzo-validation is already very good. Specifically for our case we had a bug with the validation.Each method when used with validation.By and pointers (#160), but outside of that, it's been rock solid for us.
ozzo-validation is used extensively in our commercially backed open source project https://github.com/invopop/gobl, so it felt reasonable to make the fork and but effort into ensuring we can fix any issues that appear in the future.
I'm not sure if @qiangxue still reads this, but I would like to express our appreciation for what he and all the other contributors have built up to now, and hope we can continue the high standards. Thanks!
The text was updated successfully, but these errors were encountered:
samlown
changed the title
[FORK] New fork available @ https://github.com/invopop/validation
[FORK] New fork available @ invopop/validation
Feb 24, 2023
Given the lack of updates and bug fixes in the last two years, I've taken the liberty of creating a new independent fork. We're open to Issues and Pull Requests at https://github.com/invopop/validation.
We first looked at a few of the other forks, but decided that the base version of ozzo-validation is already very good. Specifically for our case we had a bug with the
validation.Each
method when used withvalidation.By
and pointers (#160), but outside of that, it's been rock solid for us.ozzo-validation is used extensively in our commercially backed open source project https://github.com/invopop/gobl, so it felt reasonable to make the fork and but effort into ensuring we can fix any issues that appear in the future.
I'm not sure if @qiangxue still reads this, but I would like to express our appreciation for what he and all the other contributors have built up to now, and hope we can continue the high standards. Thanks!
The text was updated successfully, but these errors were encountered: