cannot use context headers in GraphQL's subscription function.

[kim-mini6]

Is my code.

final WebSocketLink websocketLink = WebSocketLink(
      'test',
      config: SocketClientConfig(
        initialPayload: {
          "headers": {},
        },
      ),
    );

I don't want to use headers in the code above.

Please look at the code below.

SubscriptionOptions(
            operationName: 'messages',
            document: gql(r'''
              subscription messages($where: messages_bool_exp!) {
                messages(where: $where) {
                  ...messagesFragment
                }
              }
                ''' +
                fragments +
                '''
            '''),
            variables: {
              "where": {
                "id": {
                  "_eq": "test",
                },
              },
            },
            fetchPolicy: FetchPolicy.cacheAndNetwork,
            context: Context().withEntry(
              HttpLinkHeaders(
                headers: headers(idToken),
              ),
            ),
          );

Here I want to add a header to the context.

For general queries other than subscriptions, the context header works fine.

error message : cannot start as connection_init failed with : Missing Authorization header in JWT authentication mode.

[micimize]

This is a known issue – you can use this workaround in the meantime

[kim-mini6]

Thanks for the answer but it's not the workaround I want

[kateile]

@micimize the workaround works amazing. will headers be added in the next WSLink?

[micimize]

@kateile after seeing the null safety v5 release to a stable version (along with its dependencies in the gql project), I do not plan on making any more feature or improvement contributions. Aside from the reasons I mentioned in #763, I have stopped using GraphQL in my own project and unfortunately it no longer makes sense for me to continue contributing here.

I haven't seen @HofmannZ or @eusdima around here in a long time so unless someone else steps in as active maintainer this project can be considered in low maintenance mode. Some people have expressed some interest in contributing in #762 but we'll see. Hopefully when I get around to the walkthrough vid it will help users PR fixes to their own problems.

[kateile]

@vincenzopalazzo can we solve this too in the coming updates?

[vincenzopalazzo]

Hi @kateile, these are some things that I can put in the queue, but do you test it with the last version of the package?

If yes, could you please propose a reproducible example?

[micimize]

@vincenzopalazzo this is more an API tweak for how to provide headers to the WebSocketLink. In essence, it would be adding a parameter to the default connect parameter, rather than requiring overriding it, so that a user could do the following:

SocketClientConfig(
  ...
- connect: (url, protocols) =>
-   IOWebSocketChannel.connect(url, protocols: protocols, headers: myCustomHeaders)
+ headers: myCustomHeaders
)

[vincenzopalazzo]

I implemented the feature suggested by @micimize (BTW thanks), in the following PR #1016

I'm releasing the new beta version (beta.6), so we will be happy to receive feedback from the users

[kim-mini6]

Thank you very much. I will always support you!