Skip to content

$recursiveRef Incorrect For Draft 2019-09 #507

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
tomdeering-wf opened this issue Feb 2, 2022 · 1 comment · Fixed by #835
Closed

$recursiveRef Incorrect For Draft 2019-09 #507

tomdeering-wf opened this issue Feb 2, 2022 · 1 comment · Fixed by #835

Comments

@tomdeering-wf
Copy link

It looks like $recursiveRef does not correctly resolve to a $recursiveAnchor with Draft 2019-09. Consider the 2019 metaschema with its vocabulary references inlined into the schema (the recommended way using $defs):

2019-09.txt (.txt extension because GitHub doesn't support .json)

Attempting to load this schema yields the following exception:
com.networknt.schema.JsonSchemaException: anyOf/$ref: Reference #/$defs/simpleTypes cannot be resolved

But this $recursiveRef should resolve without issue.

@stevehu
Copy link
Contributor

stevehu commented Feb 15, 2022

@tomdeering-wf We have a community PR to get the $recurisiveRef implemented but I am guessing there might be some gaps left. I am wondering if you could create a test case and debug into it to find the root cause and get it resolved. Thanks.

fdutton pushed a commit that referenced this issue Jul 2, 2023
stevehu pushed a commit that referenced this issue Jul 3, 2023
* Adds support for $recursiveAnchor and $recursiveRef

Resolves #507

* Updates documentation on compliance with the standards.

---------

Co-authored-by: Faron Dutton <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants