manuelwaltschek

@GabenGar I'll try to write some unit tests and will check out these cases now When I try changing it to http it complains with > Error: no schema with...

When I remove the "$schema" keyword it seems to work, but as far as I understand this keyword should be included as a best practice? How do I assert that...

@GabenGar thank you for your response. So what would be the correct way to validate a schema against 2019-09 meta schema?

@GabenGar yes I know but as the documentation states > By default this method is called automatically when the schema is added, so you rarely need to use it directly....

Thank you I will try it out Are there any docs on the get method? And what is the purpose of using Ajv2019 then?

Do you even think that is necessary? How should validateSchema behave with an instance of Ajv2019?

@epoberezkin thank you! @GabenGar but it seems that this is exactly what I need. Why wouldn't it be related to my use case? @epoberezkin why wouldn't it accept the $schema...

I think it will not quite solve my issue. For example, this is a snippet of my schema: ``` "regularHours": { "type": "array", "items": { "type": "object", "properties": { "weekday":...

I agree with you @kool79 but this is why I asked for it to be configurable. I've had this problem multiple times which was also hard to cover with tests,...

Well I guess it does, but not for sub-schemas, as it is restricted to the scope of the individual sub schemas. https://json-schema.org/understanding-json-schema/reference/object.html#additional-properties There was a feature in NetworkNt that subschemas...