[graphql_transport_ws] The new subprotocol doesn't auto-reconnect about gql HOT 2 CLOSED

Are you providing a custom graphQLSocketMessageDecoder?

It seems the Function is not properly casted, maybe a solution could be to put the ? inside the FutureOr in GraphQLSocketMessageDecoder

Current:

Proposed Solution:

typedef GraphQLSocketMessageDecoder = FutureOr<Map<String, dynamic>?> Function( 
     dynamic message); 

Could you try providing an anonymous callback to the options configuration?

TransportWsClientOptions(
  graphQLSocketMessageDecoder: (dynamic message) =>
      jsonDecode(message as String) as FutureOr<Map<String, dynamic>>?
)

Thanks!

from gql.

I'm not providing a custom graphQLSocketMessageDecoder.

The anonymous callback seems to work initially, it's not throwing error anymore. Not sure how it works with data though.

I'll close this issue after some integration tests in a few days.

Thank you

from gql.