Steve Hu
Steve Hu
The spec mentioned JSON pointer, but this field is changing so fast these days. Here is something I found in the above link. ``` Keyword Relative Location The relative location...
The major change is the structure of the message, which contains more information. I am not sure if the signature would be changed though. If yes, I agree that we...
Here is the spec section about readOnly and it should be a boolean value. We also implement it as an array just like required so that you can provide a...
Yes. The error message is a mess and I feel grateful that the spec team finally considers addressing it in a standard way. I have closed all others but keep...
When we first start the library, both JSON Path and JSON Pointer were not available. That is why I have used a specific notation for the path. I remember it...
@Gaff This would be a fantastic idea if it works. What we need to do is to add two more entries into the ValidatorTypeCode. I don't know if it works...
Some of the PRs fixed part of the issues by adding the keyword to the NonValidationKeyword here at https://github.com/networknt/json-schema-validator/blob/master/src/main/java/com/networknt/schema/JsonMetaSchema.java#L172 I am wondering if we can add the else using the...
@rhwood That warning message can be ignored. We are loading the JSON schema draft v4 for validation and that particular keyword is not supported yet. We are planning to refactor...
@alisrael I just mark the issue with `help wanted` and hope someone from the community can pick it up and get it resolved. Thanks for bringing it up.
If exclusiveMinimum is the keyword in draft 4 only, we can map this keyword to TrueValidator for v6, v7 and 2019-09. Let's wait for the test result on this issue...