test: Use Ajv to test that api‑metadata.json matches schema
#170
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Rob--W
requested changes
Jan 31, 2019
There was a problem hiding this comment.
Could you also paste examples of the output when schema validation fails?
That could even be encoded in the test, by knowingly passing an invalid API scheme to the validator, and asserting that the reported error matches with the expected error. In this way, we will know for sure that the schema validator is actually strictly enforcing the schema.
|
/ping @Rob--W |
Rob--W
reviewed
May 29, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This adds a JSON Schema for
api‑metadata.jsonand usesajvandbetter‑ajv‑errorsto validateapi‑metadata.jsonagainstapi‑metadata.schema.json.review?(@Rob--W)