Subscription transport protocol has wrong casing

[cotillion]

It appears 3.3 broke the serialization of the transport protocol.
Even the sample project is giving: Error: Invalid message type!

This appears to happen because 'type' is now 'Type'

{"Id":null,"Type":"connection_ack","Payload":null}

The structure is supposed to be:

export interface OperationMessage {
  payload?: any;
  id?: string;
  type: string;
} 

I belive this was broken by #174
The DocumentWriter appears to use the MVC JSON serialization settings. These could perhaps be used for the Payload but not for the OperationMessage itself.

[benidi]

I have the same problem. In subscriptions-transport-ws i get errors when receiving messages.

[HakuTheWolfSpirit]

@DSilence FYI

[DSilence]

Yeah, it looks like my changes broke it. Given that graphql client libraries (at least for now) are so strict about case, the case should be fixed for those messages, either via custom serializer (same as for ExecutionResult) or via serialization attributes. If the contributors don't mind, I'll be happy to provide the PR with a fix.

[pekkah]

Could you test the latest preview package?

[benidi]

Looks good to me. Subscriptions with apollographql/subscriptions-transport-ws now working again.

[cotillion]

Works! Thanks @DSilence!