This repository has been archived by the owner on Feb 25, 2021. It is now read-only.
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.
Inspired by #7 and in response to the
json_schema
gem not properly validating nested objects, this PR switches the json_schema gem with the json-schema gem.We found this issue when there was an OpenAPI spec file with an invalid HTTP method type.
Despite the spec defining the allowed values in /resources/swagger_meta_schema.json#L306-L343, those rules were not being enforced by the
json_schema
gem and the invalid spec was considered valid. Using thejson-schema
gem, validation was performed properly:Also, fixed some of the descriptions in
valid_spec.yaml
that were copy pasted.@drewolson @jfeltesse-mdsol @jcarres-mdsol @ykitamura-mdsol