json-schema-validator
json-schema-validator copied to clipboard
networknt
A fast Java JSON schema validator that supports draft V4, V6, V7, V2019-09 and V2020-12
Hi, I see that the [EmailValidator](https://github.com/networknt/json-schema-validator/blob/master/src/main/java/com/networknt/org/apache/commons/validator/routines/EmailValidator.java?plain=1#L52) is limiting the user length in an email to be less than or equal to 64 [Ref](https://github.com/networknt/json-schema-validator/blob/master/src/main/java/com/networknt/org/apache/commons/validator/routines/EmailValidator.java?plain=1#L224-230), I was wondering if there is a...
Closes #1034 Validate `allOf`, `oneOf` and `anyOf` contains array
Our console is currently being spammed with the debug message from the `BaseJsonValidator`. It would be great if you could set a boolean to turn off this message, as we...
We have encountered an issue with the schema validation where it does not correctly enforce the schema structure, specifically for cases where the type of certain properties is incorrect. For...
Below schema doesn't work for me with V201909 and latest version of jar. ``` { "type": "object", "properties": { "datetime": { "type": "string", "format": "date-time" } }, "required": ["datetime"] }...
Library is giving error **java.lang.UnsupportedOperationException: No suitable validator for id** PFA java class to reproduce issue version 1.4.0 and 1.5.0. Issue is not produced in old version of library version...
Currently in the version 1.5.0 (even before) the `module-info.class` is located at `META-INF/versions/9/module-info.class` which is wrong. It must be located in the root of the JAR file .... References: *...
I am currently trying to validate an OpenAPI 3.0 document using the `json-schema-validator` library and I am getting the following warning when creating the `JsonSchema` object: ``` [main] WARN com.networknt.schema.UnknownKeywordFactory...
We are trying to upgrade this library from `1.1.0` to `1.5.7`. Earlier we used to get the fully qualified json path in the error. However this behaviour seems to be...
