v10 does not allow typing on custom getRequest method in class with extended AuthGuard

[kpervin]

Did you read the migration guide?

• I have read the whole migration guide

Is there an existing issue that is already proposing this?

• I have searched the existing issues

Potential Commit/PR that introduced the regression

No response

Versions

9.0.3 -> 10.0.1

Describe the regression

Previously, there was no typing for getRequest on the AuthGuard class in 9.0.3. However, in 10.0.1, typing was introduced. The typing introduced conflicts with the ability to get the req variable from a GraphQL request when "noImplicitReturns": true is set in tsconfig.json. The only way that I have found to get rid of the error is to introduce @ts-expect-error or @ts-ignore. As such, I cannot use the code used in the Passport example in the NestJS docs.

Minimum reproduction code

import { IncomingMessage } from "http";
import { GqlExecutionContext } from "@nestjs/graphql";

/**
 * Global [guard](https://docs.nestjs.com/guards) for GraphQL requests.
 *
 * @see https://docs.nestjs.com/recipes/passport#graphql
 */
@Injectable()
export class GqlAuthGuard extends AuthGuard([
 ...
]) {  
  getRequest(context: ExecutionContext): IncomingMessage {
    const ctx = GqlExecutionContext.create(context);
    return ctx.getContext<{ req: IncomingMessage }>().req;
  }
  ...
}

Expected behavior

Allow the ability to type the getRequest method without errors thrown.

Other

The error thrown with the above example is as follows:

TS2416: Property  getRequest  in type  GqlAuthGuard  is not assignable to the same property in base type  IAuthGuard 
Type
(context: ExecutionContext) => IncomingMessage
is not assignable to type  <T = any>(context: ExecutionContext) => T 
Type  IncomingMessage  is not assignable to type  T 
 T  could be instantiated with an arbitrary type which could be unrelated to  IncomingMessage

[kamilmysliwiec]

Fixed in 10.0.2