Skip to content

output schema fixes #940

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

Conversation

karenetheridge
Copy link
Member

Fixed some errors in output/schema.json

it is possible to have both $ref and $recursiveRef in the traversed schema path
@gregsdennis
Copy link
Member

@karenetheridge Could you link to the portions of the spec that this file references, please? Just to make sure that this change is valid.

@karenetheridge
Copy link
Member Author

@gregsdennis
Copy link
Member

gregsdennis commented May 27, 2020

@karenetheridge thanks, but I mean the output portions. Where are the schema and instance that generated the output (they're in the spec, but I'm too busy to find them right now)?

The pattern should merely be an annotation of the pattern provided in the schema, so if you change the example output, you need to change the example schema that should generate the output.


Oh... this is the schema that describes the output format... nvm.

@@ -46,18 +46,18 @@
},
{
"if": {
"oneOf": [
"anyOf": [
Copy link
Member

Choose a reason for hiding this comment

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

Why this change? Are you expecting $ref and $recursiveRef to both appear in the keyword location?

... I suppose they could....

okay.

Copy link
Member Author

Choose a reason for hiding this comment

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

sure, if there is a $recursiveRef in the subschema at the other end of a $ref, it could certainly happen.

I have a test case with .../$ref/$ref/$ref/$ref/.. :) -- https://github.com/karenetheridge/JSON-Schema-Draft201909/blob/master/t/errors.t#L788

@handrews handrews added this to the draft-08-patch1 milestone May 31, 2020
karenetheridge added a commit to karenetheridge/JSON-Schema-Modern that referenced this pull request Jun 1, 2020
These are all required for validation against the metaschemas to succeed.

    json-schema-org/json-schema-spec#923 (fixes to output/schema.json)
    json-schema-org/json-schema-spec#940 (not yet merged; another fix to output/schema.json)
karenetheridge added a commit to karenetheridge/JSON-Schema-Modern that referenced this pull request Jun 2, 2020
These are all required for validation against the metaschemas to succeed.

    json-schema-org/json-schema-spec#923 (fixes to output/schema.json)
    json-schema-org/json-schema-spec#940 (not yet merged; another fix to output/schema.json)
karenetheridge added a commit to karenetheridge/JSON-Schema-Modern that referenced this pull request Jun 2, 2020
These are all required for validation against the metaschemas to succeed.

    json-schema-org/json-schema-spec#923 (fixes to output/schema.json)
    json-schema-org/json-schema-spec#940 (not yet merged; another fix to output/schema.json)
@Relequestual
Copy link
Member

@gregsdennis If you'll approve, let's merge this?

@Relequestual Relequestual merged commit 5c57e99 into json-schema-org:master Jul 17, 2020
@karenetheridge karenetheridge deleted the ether/output-schema-fixes branch July 17, 2020 17:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Development

Successfully merging this pull request may close these issues.

4 participants