Using operationName immediately closes the connection

Using operationName variable in client.subscribe immediately closes the connection

{
  query,
  variables,
  extensions: {
    userId: context?.userId,
  },
  operationName: context?.rootOperationInfo?.operationName,
}

As soon as I remove the operationName, it works. I’m using version “graphql-ws”: “^4.7.0” As a workaround I am using

{
  query,
  variables,
  extensions: {
    userId: context?.userId,
  operationName: context?.rootOperationInfo?.operationName,
  },
}

Please let me know if you need more info.

[quant-daddy]

Okay so in the error cb here

{
  next: (data) => {
    pending.push(data);
    deferred && deferred.resolve(false);
  },
  error: (err: Error) => {
    console.log(err);

    error = err;
    deferred && deferred.reject(error);
  },
  complete: () => {
    done = true;
    deferred && deferred.resolve(true);
  },
}

I get the error [ { message: 'Unable to identify operation' } ] thrown from the line here. I think I know why the error occurs: the operation name in the document is actually not context?.rootOperationInfo?.operationName for a workaround that I am using 😃

[enisdenjo]

Just surround your server callbacks with a try/catch and log the caught errors.