Properly support propertyNames #396
Comments
JonasProgrammer
added a commit
to JonasProgrammer/json-schema-validator
that referenced
this issue
Apr 11, 2021
- implement property names in terms of full schema validation - add test case for complex property name - added test case for networknt#342 - fix networknt#375 tests to expect standard messages - closes networknt#396 - closes networknt#342
JonasProgrammer
added a commit
to JonasProgrammer/json-schema-validator
that referenced
this issue
Apr 11, 2021
- implement property names in terms of full schema validation - add test case for complex property name - added test case for networknt#342 - fix networknt#375 tests to expect standard messages - closes networknt#396 - closes networknt#342
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The current implementation of
propertyNamesis completely separate from the remaining validation code, implementing special cases for stuff likeminLength.According to the spec, however,
propertyNamesshould be treated like a normal json schema being applied to a text node of the property value.This has lead to issues, such as #342 and #326.
I propose to just do what the spec says and apply the node content under
propertyNamesto each field name as if it were aTextNode.The text was updated successfully, but these errors were encountered: