accept null values in order_by input field (fix #2754) #2755
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.
Description
The server used to throw
500 Internalerror whennullvalue is provided against input fields in<table-name>_order_byinput object.Query:-
Response:-
{ "errors": [ { "extensions": { "path": "$.selectionSet.article.args.order_by", "code": "unexpected" }, "message": "unexpected null for ty 'order_by'" } ] } This PR fixes this issue.Affected components
Related Issues
fixes #2754
Solution and Design
Maybevalues for all input fields underorder_byinput. The value isNothingwhennullis provided. Omit the input ifNothingis found.Steps to test and verify
Follow the test case added in this PR