Signature Mismatch in `MiddlewareInterface` about routing-controllers

[pleerock]

new middleware interface signatures are being added in #119

[pleerock]

Not sure what is possible there. I know about this issue with typescript, one solution can be if we create two separate interfaces KoaMiddlewareInterface and ExpressMiddlewareInterface instead of MiddlewareInterface. If you can come to solution with MiddlewareInterface please let me know

[JD-Robbs]

If I can work out a way to keep it all in one interface, I'll let you know. I'll take another look and maybe check if anyone on StackOverlow has any ideas.

[marshall007]

@JD-Robbs I was able to get it to compile by overloading the method on my custom class with a more generic signature:

@Middleware()
export class CustomerHeader implements MiddlewareInterface {

  use(request: any, response: any, next?: (err?: any) => any): any;
  use(request: Request, response: Response, next?: NextFunction): any {
    // ...
    next();
  }

}

@pleerock I think if you annotate MiddlewareInterface with the additional overloads it should allow users to implement the method with or without typed parameters.

[pleerock]

middlewares now have separate signatures in 0.7.0

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.