Adds support for AJV Keywords + conditional schemas #8
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.
Coming from #5, rebased on top of #7
This PR brings the current version I plan to use in production for a while to upstream:
On the last one, the current implementation assumes the schema has a structure with a limited number of predefined of keywords (headers, body, query ...), but will not allow for conditionals such as if: and then: (see more here). That feature is particularly useful in a versioned API, if we want to maintain backwards compatibility without carrying too much schema weigh around.
I hope the test explains it well. The implementation is kind of simple, we may want to generalize it a bit.