-
Notifications
You must be signed in to change notification settings - Fork 2.8k
Closed
Labels
c/actionsRelated to actionsRelated to actionsc/serverRelated to serverRelated to servere/easycan be wrapped up in a couple of dayscan be wrapped up in a couple of days
Milestone
Description
Hasura is not checking response from action handler. Field in schema marked as non nullable, e.g.:
type SampleOutput {
accessToken : String!
userId : Int!
}
and badly implemented handler which doesn't return mandatory fields cause response:
{
"data": {
"actionName": {
"accessToken": null,
"userId": null
}
}
}
Schema should be accepted and thus bad answer from resolver can be ignored. In this way works other GraphQL servers like Apollo or GraphQL JS.
Metadata
Metadata
Assignees
Labels
c/actionsRelated to actionsRelated to actionsc/serverRelated to serverRelated to servere/easycan be wrapped up in a couple of dayscan be wrapped up in a couple of days