Rishabh Maheshwari

@fdutton The bundled 2019-09 draft meta schema: https://gist.github.com/gareth-robinson/815239b36e397e484b77141b912d1b28, in https://github.com/networknt/json-schema-validator/issues/475#issuecomment-976306236 was very helpful for validating json schema against meta schema. Could you also provide a similar json for 2020-12 draft...

The bundled 2019-09 draft meta schema: https://gist.github.com/gareth-robinson/815239b36e397e484b77141b912d1b28, in https://github.com/networknt/json-schema-validator/issues/475#issuecomment-976306236 was very helpful for validating json schema against meta schema. Could someone provide a similar json for 2020-12 draft ? Otherwise,...

thanks @fdutton. It worked. However, it's not giving any validation errors for below data which is invalid as per draft 2020-12 : ```json { "type": "object", "properties": { "key": {...

Thanks! Will wait for a fix for 2020-12.

Thanks @justin-tay for fixing this in https://github.com/networknt/json-schema-validator/pull/931 https://github.com/networknt/json-schema-validator/issues/475#issuecomment-1618381541 now gives me below errors: * `Json schema: $.properties.key.type: does not have a value in the enumeration [array, boolean, integer, null, number,...

Agreed! Thanks for the explanation This issue can be closed from my side.

+1. `dependentRequired` and `dependentSchemas` are keywords from these new specifications required in my project. In `2019-09` and `2020-12` specifications, keyword `dependencies`, which formly supports, is replaced by `dependentRequired` and `dependentSchemas`....