You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When the query sent to server uses variables, non-nullable types are not validated. I've tested it only on schema-first approach.
To Reproduce
Let say we have the following schema:
"Input used for posting a message to server."inputMessageInput {
"The author of the message."author: String!"The content of the message."content: String!
}
typeMessage {
...
}
"One of the three root graph nodes. It's used for posting data to server."typeMutation {
"It's used to post a message to server."createMessage(
"The message that will be posted to server."input: MessageInput!
): Message!
}
typeQuery {
...
}
The Query and Message types aren't important. Let's assume we have them written in a right way.
You can see that the field content is not populated.
The Resolver is invoked with Author: "Random author here." and Content:null.
Expected behavior
The Resolver should not be invoked because the content field of the MessageInput graph type is marked as String!. The Executer should throw an error because we've inserted an invalid query.
Desktop:
Ubuntu
18.10
Additional context
Used package version: 0.8.1-rc2
The text was updated successfully, but these errors were encountered:
Describe the bug
When the query sent to server uses variables, non-nullable types are not validated. I've tested it only on schema-first approach.
To Reproduce
Let say we have the following schema:
When the following query is executed:
The Resolver is invoked with
Author
:"Random author here."
andContent
:null
.Expected behavior
The Resolver should not be invoked because the
content
field of theMessageInput
graph type is marked asString!
. The Executer should throw an error because we've inserted an invalid query.Desktop:
Additional context
Used package version: 0.8.1-rc2
The text was updated successfully, but these errors were encountered: