Stamping JSON Schema definitions with unique IDs #111
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Committer Notes
Reports indicate that not all JSON Schema validation engines are tolerant of context-dependent definition names; they have to be globally unique so we get errors for multiple definitions of (say)
#/definitions/title
when a metaschema source has multiple local definitions for assemblies or fields of that name.This patch addresses this by adding an (arbitrary) generated identifier to stamp each definition with an identifier peculiar to its origin in the source.
Needs testing.
All Submissions:
Changes to Core Features: