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
{{ message }}
This repository has been archived by the owner on Apr 14, 2023. It is now read-only.
So which way do we want to do it? With or without payload?
Because our backend implementation now implements the first version like specified in the README and I'm wondering why subscriptions-transport-ws is throwing errors.
The text was updated successfully, but these errors were encountered:
This is an error in the documentation. All messages from the server should be in the form {type, id, payload}. If you want to put together a PR, I'd be happy to review it.
timsuchanek
added a commit
to timsuchanek/subscriptions-transport-ws
that referenced
this issue
Jan 28, 2017
For the
SUBSCRIPTION_FAIL
event, the README says the following:errors: Array<Object>
: array of errors attributed to the subscription failing on the serverid: string
: subscription ID of the subscription that failed on the serverSo I assume, that the message should look like this:
But the client implementation apparently wants this:
https://github.com/apollostack/subscriptions-transport-ws/blob/master/src/client.ts#L224
So which way do we want to do it? With or without payload?
Because our backend implementation now implements the first version like specified in the README and I'm wondering why
subscriptions-transport-ws
is throwing errors.The text was updated successfully, but these errors were encountered: