json-schema-validator
json-schema-validator copied to clipboard
A fast Java JSON schema validator that supports draft V4, V6, V7, V2019-09 and V2020-12
Hi We have a schema that doesn't use `required` field. Instead, we have a `optional` flag on each property to check if its a required field or not. It is...
I was previously using the following version of the JSON Schema Validator and everything was working fine when I was validating the JSON against the respective JSON Schema: com.networknt json-schema-validator...
It looks like a major version should have been used, this seems like a major change to me. Is there any guide about how to proceed to upgrade?
Using the validator `Set validationMessages = jsonSchema.validate(jsonNode);`, we get the following error [in our build on GitHub within a unit test](https://github.com/aws-powertools/powertools-lambda-java/actions/runs/6417845031/job/17424409856?pr=1456#step:4:5120), but not locally. No problem with other schema versions...
1.3.0 introduced a breaking change to a public interface of `JsonSchema` `getCurrentUri()` is no longer available, breaking code that used it. That is usually a major version bump.
Consider the following schema: ``` { "type": "object", "properties": { "id": { "type": "string", "format": "uuid" } } } ``` Using UUID as defined here: https://json-schema.org/draft/2019-09/json-schema-validation#rfc.section.7.3.5 Validating the following JSON...
Consider the following schema: ``` { "type": "object", "properties": { "creation_date": { "type": "string", "format": "date-time" } } } ``` The following JSON should not be valid but it is:...
HI, i'm using version 0.1.18 and i'm caching the json schemas within a static block in java .While doing so all the schemas are not getting cached and the error...
Greetings - Similar to the use case described in https://github.com/networknt/json-schema-validator/issues/285, we're looking to validate a schema against the specification meta schema to ensure it is syntactically valid. And then later...
Please revert fix made in scope of #815. This fix was deployed based on incorrect assumption that java works incorrectly with regexp. But actually issue is not in java. Issue...