Add webSocket object to subscription context function (fixes #393)

[tpetry]

The subscription context callback function is only receiving the connection object but missing the webSocket object containing the WebSocket Upgrade Request.

[tpetry]

This will fix #393

[stale]

Due to inactivity of this issue we have marked it stale. It will be closed if no further activity occurs.

[joealden]

This PR should be kept open, I don't understand why stale bot will close it 'if no further activity occurs'. This is is still a feature that I think would be a worthy addition to graphql-yoga, but no maintainer has responded to this PR yet and said why it is or isn't mergeable. Why should it be closed?

[tpetry]

4 months, a single line of code change, completely backwards compatible. where is the problem?

[joealden]

@tpetry I think the issue is that the Prisma devs aren't really currently focused on maintaining graphql-yoga :/

[tpetry]

Many commits (!) have been made in the last 4 months.

@maticzav What do we have to do to get this simple change merged?

[joealden]

@maticzav @schickling Again, there has been no movement on this PR in over a month, and there has been no response from any maintainer since the PR was made, which was nearly 6 months ago.

It is getting pretty annoying to maintain a fork for this seemly simple change.

As @tpetry and I have said already, what is preventing this from being merged?

[beaumontjonathan]

Any progress with this, or any decent work arounds?

[stale]

Due to inactivity of this issue we have marked it stale. It will be closed if no further activity occurs.

[luis-rocha]

Well, I need this, too. Bringing it back from stale status

[stale]

Due to inactivity of this issue we have marked it stale. It will be closed if no further activity occurs.

[stale]

Hey 👋, It seems like this issue has been inactive for some time. In need for maintaining clear overview of the issues concerning the latest version of graphql-yoga we'll close it.
Feel free to reopen it at any time if you believe we should futher discuss its content. 🙂

[gbouteiller]

up