Fix raising exception on multiple schemas #119
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.
Hello! I'm unsure of the intended behavior of this library when multiple schemas are provided for an endpoint, but I do know a
KeyError
occurs when one schema fails before another is processed (in my case when a failed to validate request schema precedes a successful query schema). I updated the way the errors are added onto theBadRequest
by just merging theschema_errors
from all the failing schemas inside ofBadRequest.data['errors']['schema_errors']
.This is the error when using both request and query validation and request fails: