Skip to content

dynamic $recursiveRef test with cousin $recursiveAnchors #489

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

Merged
merged 1 commit into from
Jun 7, 2021

Conversation

karenetheridge
Copy link
Member

No description provided.

@karenetheridge karenetheridge requested a review from a team June 6, 2021 21:21
Copy link
Member

@gregsdennis gregsdennis left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I thought we already had this (or maybe we just talked about it in slack).

@karenetheridge karenetheridge force-pushed the ether/more-recursiveRef branch from f8a5668 to 7c33b53 Compare June 6, 2021 21:37
@karenetheridge
Copy link
Member Author

karenetheridge commented Jun 6, 2021

I think this one came out of a discussion as to whether it was possible to (always) predict the path a $recursiveRef would take simply by inspecting the schema. I was going through my old test cases and all the other ones for $recursiveRef had been incorporated into the test suite, except for this one.

@karenetheridge karenetheridge merged commit eaa5bff into master Jun 7, 2021
@karenetheridge karenetheridge deleted the ether/more-recursiveRef branch June 7, 2021 04:53
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 this pull request may close these issues.

2 participants