Noah Ruben

This issue and #285 occurs because of https://github.com/networknt/json-schema-validator/blob/d5a861affba41159f1c4187662144297fe7cf8c8/src/main/java/com/networknt/schema/PropertiesValidator.java#L33. This assumes that all field names are in the schema file. This is not the case for the 2019 Meta-Schemas where the...

> Thanks @stevehu! I got this working using a meta schema. > > Just a side note, our system allows for super users to create their own schemas as we...

```JSON { "$id": "https://example.com/person.schema.json", "$schema": "https://json-schema.org/draft/2019-09/schema", "title": "Person", "type": "object", "additionalProperties": false, "properties": { "firstName": { "type": "string", "minLength": 3, "description": "The person's first name." }, "lastName": { "type": "string",...

@stevehu can you reopen this issue? The behavior of the validation of nested keywords isn't consistent.

@stevehu I've created a gist to showcase my problem: [ValidationTests.java](https://gist.github.com/SirMoM/d748ad3f0607122d92debe29fd90c039). I hope this helps to understand the problem. If you need any additional Information please contact me.

I've continued the discussion in #313.