Closed dpaola2 closed 6 years ago
Hello!
Using the graphql-ruby gem and subscriptions. When a subscription response is empty, the Apollo library seems to assume a response, when there is no such response. So an exception is thrown.
Specifically, this line seems to be the culprit.
See https://github.com/rmosolgo/graphql-ruby/issues/1362 for original discussion.
I'm closing the issue since it was fixed in v1.7.14 https://github.com/rmosolgo/graphql-ruby/pull/1382. In case of exceptions, graphql-ruby will set the result value to {} instead of nil.
v1.7.14
graphql-ruby
{}
nil
Hello!
Using the graphql-ruby gem and subscriptions. When a subscription response is empty, the Apollo library seems to assume a response, when there is no such response. So an exception is thrown.
Specifically, this line seems to be the culprit.
See https://github.com/rmosolgo/graphql-ruby/issues/1362 for original discussion.