-
Notifications
You must be signed in to change notification settings - Fork 78
feat: add support for not-in and not-eq query operators #202
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
10 commits
Select commit
Hold shift + click to select a range
fa3a6c4
feat: add support of not-in and not-eq
HemangChothani 192f6b1
Merge branch 'master' into firestore_issue_189
crwilcox 172c251
Merge branch 'master' into firestore_issue_189
crwilcox 394b5e3
Merge branch 'master' of https://github.com/googleapis/python-firesto…
HemangChothani 965eb7f
Merge branch 'master' into firestore_issue_189
tseaver 700a1ad
Merge branch 'firestore_issue_189' of https://github.com/q-logic/pyth…
HemangChothani 57b4152
Merge branch 'master' of https://github.com/googleapis/python-firesto…
HemangChothani 420788b
fix: unit test
HemangChothani fba9e17
Revert "fix: unit test"
HemangChothani 25ac050
fix: update query-invalid-operator.json file
HemangChothani File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
does this method also accept "not-in, array_contains" and more? This may be accurate, but I wanted to double check :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@crwilcox Yes, this method accept all the values including
array_contains
we don't have any special condition for that, limitation of acceptable values are just mentioned in doc-string.Is this question related to #203 issue?