Sorting

• I'm submitting a ...

  • bug report
  • feature request
  • support request

• I confirm that I

  • used the search to make sure that a similar issue hasn't already been submit

Expected Behavior

When typing my APIs, I noticed that I could type alias my TsoaResponse parameters since the same types are used in multiple routes.

export type NotFound = TsoaResponse<
  404,
  { reason: "Thing does not exists" }
>;

@Route("stuff")
export class MyController extends Controller {
  @Patch("{id}")
  public update(
    @Path() id: number,
    @Res() notExistsResponse: NotFound,
  ): Promise<any> {
    // update thing ... 
    return notExistsResponse(404, { reason: "Thing does not exists" });
  }

  @Get("{id}")
  public get(
    @Path() id: number,
    @Res() notExistsResponse: NotFound,
  ): Promise<any> {
    // get thing ... 
    return notExistsResponse(404, { reason: "Thing does not exists" });
  }
}

Current Behavior

However, the Res decorator seems to limit this to the TsoaResponse type without accepting aliases or extended interfaces.

Generate routes error.
2024-08-27 16:27:11 [1]  GenerateMetadataError: @Res() requires the type to be TsoaResponse<HTTPStatusCode, ResBody>
2024-08-27 16:27:11 [1] At: ...

Possible Solution

Let the Res decorator accept more types. Not sure how to do that since I am not that used to typescript.

Steps to Reproduce

See example above.

Context (Environment)

Version of the library: 6.4.0
Version of NodeJS: v20.12.2

• Confirm you were using yarn not npm: [x]

Detailed Description

None

Breaking change?

Not sure