feat: additional query (_q) to return 400 in case fields not included in the schema #127
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
danibix95
added
enhancement
added 10 commits
September 11, 2023 12:44
danibix95
force-pushed
the
edit/invalid-mongo-query-to-return-400
branch
from
1b78f26 to
bfcaa73
Compare
danibix95
approved these changes
Sep 11, 2023
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.
Pull Request Type
Description
Every method requesting to parse the content of the _q query parameter now returns a 400 Bad Request in case there's at least one field not included in the JSON Schema of the collection (before the exception was not handled, and a 500 was returned).
Closes #55 .
PR Checklist
Does this PR introduce a breaking change?
We consider this as a breaking change because of the different HTTP response status code.
Other information