Basic custom query filters #103
Merged
Conversation
This file contains hidden or 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
|
@eduarde : Thanks for this one, and it seems make sense to have a light way to do it. |
arunsureshkumar
pushed a commit
to arunsureshkumar/graphene-mongo
that referenced
this pull request
Nov 2, 2020
…_filters Basic custom query filters
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.
These are pretty much the same changes from the following closed pr #88. Kudos to @arunsureshkumar ! I totally agree with you @abawchen , for advanced mongo filters maybe the graphene-mongo-extras is a much better choice. However, from my point of view, if you like to make queries with some basic custom filters, it is more convenient to create those filters on your side instead of relying on other library to accomplish that. What do you think ?