[OUTDATED] use SocketClientConfig.connect instead. old work around to headers for graphql flutter

redirect.md

A custom link is no longer necessary – use SocketClientConfig.connect instead.

If you want to view the outdated, probably no-longer working solution, see the previous version

@kateile I admit I didn't read all that but gql_dio_link's been migrated to nullsafe+v4 so hopefully that will solve your issue.

I still face some issues. Please see my comment here

I did some little mistakes and I finally solved. Thank you so much

good to hear 👍

how do i apply this solustion to WSclient ?

final WSLink _webSocketLink = WSLink('ws://IP_ADDRESS/graphql',
config: SocketClientConfig(
autoReconnect: true,
inactivityTimeout: null,
),
headers: {"authorization": "exampletoken"});

final Link _link = _webSocketLink;
final GraphQLClient _client = GraphQLClient(
link: _link,
cache: GraphQLCache(),
);

i did try but still unable to connect
any idea @kateile?

please help

@dunods Use SocketClientConfig.connect – this is outdated and probably won't work now

@micimize .. im using the old version graphql_flutter: ^4.0.0 and still yet that code didnt work out.. any idea how to make it work

probably some dev environment setup issue, but I really recommend upgrading at least to 4.1.0-beta.1.

I no longer contribute to graphql_flutter so I don't have the details fresh in my head anymore