Skip to content
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: delegate - data does not exist in value #150

Merged
merged 1 commit into from
Aug 28, 2018
Merged

fix: delegate - data does not exist in value #150

merged 1 commit into from
Aug 28, 2018

Conversation

sheepsteak
Copy link

When trying to use subscriptions through a GraphQL binding I kept getting an error that 'data' was undefined. After some debugging I found that value does not have data property inside it that the delegateSubscription function was relying on.

I found that the data property is already extracted in the pushValue function of apollographql/graphql-tools. So whatever gets returned on line 87 is already the contents of data.

With the small change in this PR and the fix in ardatan/graphql-tools#928 I was able to get subscriptions working from my GraphQL server talking to a Hasura GraphQL server via a binding.

@jevakallio
Copy link

@nikolasburk @schickling this looks like a pretty clear-cut bug and fix IMO, any chance this could be landed & patched? It's a blocking issue for my team.

@feynmanliang
Copy link

Thanks for this, I reported this in #153 and this fixes that issue!

@feynmanliang feynmanliang mentioned this pull request Aug 22, 2018
@marktani
Copy link

Thanks a lot for this PR, we'll review this soon 👍

@divyenduz
Copy link
Collaborator

@sheepsteak : Thanks for the PR. Looks good to me 👍

@divyenduz divyenduz merged commit 3f79a79 into dotansimha:master Aug 28, 2018
@divyenduz
Copy link
Collaborator

divyenduz commented Aug 28, 2018

This is released in graphql-binding 2.2.4 🎉

Used by prisma-binding 2.1.5

@simonjoom
Copy link

simonjoom commented Aug 29, 2018

yeah guy finally it's released..., i spent more than one week to figure out this problem (i thought was from my implementation) ... subscriptions who does not work is very pity for prisma... Do you test your api properly before to get out a update?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants