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
Using the library we have find this scenario. It allows negative numbers with this definition. It works well for the other constraints but no for check the minimum constraint.
The text was updated successfully, but these errors were encountered:
luigimoyano
changed the title
It don't validate negative numbers with oneOf definition
It don't validate minimum constratint with oneOf definition for integer or number types
Apr 10, 2018
@luigimoyano the current version of the master branch doesn't have this issue. I've used your schema as defined above and when trying to validate using the code snippet below you can see in the output there is an error with regards to the minimum value.
In an attempt to cleanup this repo we are trying to filter the issues and see which ones might be closed. Is it safe to assume this is a rather old issue, which sadly was left unanswered, but can be closed? Feel free to close it yourself with some comments if helpful.
array(4) {
[0]=>
string(45) "Integer value found, but a string is required"
[1]=>
string(50) "Does not have a value in the enumeration ["Ample"]"
[2]=>
string(52) "Must have a minimum value greater than or equal to 0"
[3]=>
string(34) "Failed to match exactly one schema"
}
Using the library we have find this scenario. It allows negative numbers with this definition. It works well for the other constraints but no for check the minimum constraint.
The text was updated successfully, but these errors were encountered: