-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
fix(GraphQL): This PR fix panic error when we give null value in filter connectives. #6707
Conversation
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.
LGTM. 32 rules errored during the review.
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.
LGTM. 33 rules errored during the review.
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.
LGTM. 11 rules errored during the review.
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.
Reviewed 2 of 2 files at r1.
Reviewable status: complete! all files reviewed, all discussions resolved (waiting on @MichaelJCompton)
…er connectives. (#6707) Fixes GRAPHQL-744 This PR fix panic error when we give null value in filter connectives. Null values corresponding to connective are skipped now. For example in the below filter, not connective gets skipped. ``` filter:{ id:{eq:"123"}, not:null }, ```
…er connectives. (#6707) Fixes GRAPHQL-744 This PR fix panic error when we give null value in filter connectives. Null values corresponding to connective are skipped now. For example in the below filter, not connective gets skipped. ``` filter:{ id:{eq:"123"}, not:null }, ``` (cherry picked from commit 345b6d1)
…er connectives. (#6707) Fixes GRAPHQL-744 This PR fix panic error when we give null value in filter connectives. Null values corresponding to connective are skipped now. For example in the below filter, not connective gets skipped. ``` filter:{ id:{eq:"123"}, not:null }, ``` (cherry picked from commit 345b6d1)
…er connectives. (#6707) Fixes GRAPHQL-744 This PR fix panic error when we give null value in filter connectives. Null values corresponding to connective are skipped now. For example in the below filter, not connective gets skipped. ``` filter:{ id:{eq:"123"}, not:null }, ``` (cherry picked from commit 345b6d1)
…er connectives. (#6707) Fixes GRAPHQL-744 This PR fix panic error when we give null value in filter connectives. Null values corresponding to connective are skipped now. For example in the below filter, not connective gets skipped. ``` filter:{ id:{eq:"123"}, not:null }, ``` (cherry picked from commit 345b6d1)
…er connectives. (#6707) (#6736) Fixes GRAPHQL-744 This PR fix panic error when we give null value in filter connectives. Null values corresponding to connective are skipped now. For example in the below filter, not connective gets skipped. ``` filter:{ id:{eq:"123"}, not:null }, ``` (cherry picked from commit 345b6d1)
…er connectives. (#6707) (#6729) Fixes GRAPHQL-744 This PR fix panic error when we give null value in filter connectives. Null values corresponding to connective are skipped now. For example in the below filter, not connective gets skipped. ``` filter:{ id:{eq:"123"}, not:null }, ``` (cherry picked from commit 345b6d1)
Fixes GRAPHQL-744
This PR fix panic error when we give null value in filter connectives. Null values corresponding to connective are skipped now.
For example in the below filter,
not
connective gets skipped.This change is
Docs Preview: