Skip to content

Add tests for location-independent identifiers in remote ref #454

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
wants to merge 2 commits into from
Closed

Add tests for location-independent identifiers in remote ref #454

wants to merge 2 commits into from

Conversation

Stranger6667
Copy link
Contributor

As briefly discussed in Slack, here are tests that verify that location-independent identifiers work when they are inside a remote schema.

@Julian
Copy link
Member

Julian commented Jun 21, 2022

Sorry this took so long :/ but yeah, merged. Appreciated!

@Julian Julian closed this Jun 21, 2022
@Stranger6667 Stranger6667 deleted the dd/add-location-independent-ids-tests branch June 21, 2022 14:33
@Stranger6667
Copy link
Contributor Author

Thank you!

davishmcclurg added a commit to davishmcclurg/json_schemer that referenced this pull request May 16, 2023
This will keep using the same draft for any remote `$ref` schemas that
don't explicitly set `$schema`. It's necessary so that we know which
keywords to use for things that have changed between drafts (eg, `id`
vs. `$id`).

Exposed by: json-schema-org/JSON-Schema-Test-Suite#454
davishmcclurg added a commit to davishmcclurg/json_schemer that referenced this pull request May 16, 2023
This will keep using the same draft for any remote `$ref` schemas that
don't explicitly set `$schema`. It's necessary so that we know which
keywords to use for things that have changed between drafts (eg, `id`
vs. `$id`).

Exposed by: json-schema-org/JSON-Schema-Test-Suite#454
davishmcclurg added a commit to davishmcclurg/json_schemer that referenced this pull request May 22, 2023
This will keep using the same draft for any remote `$ref` schemas that
don't explicitly set `$schema`. It's necessary so that we know which
keywords to use for things that have changed between drafts (eg, `id`
vs. `$id`).

Exposed by: json-schema-org/JSON-Schema-Test-Suite#454
davishmcclurg added a commit to davishmcclurg/json_schemer that referenced this pull request May 26, 2023
This will keep using the same draft for any remote `$ref` schemas that
don't explicitly set `$schema`. It's necessary so that we know which
keywords to use for things that have changed between drafts (eg, `id`
vs. `$id`).

Exposed by: json-schema-org/JSON-Schema-Test-Suite#454
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.

4 participants