Middleware Execution Order is Reversed

[winrid]

As title says...

Example:

function middlewareOne(req: express.Request, res: express.Response, next: () => void): void {
    console.log('one');
    next();
}

function middlewareTwo(req: express.Request, res: express.Response, next: () => void): void {
    console.log('two');
    next();
}

@Route("comments")
export class CommentsController extends Controller {
    @Get("{tenantId}")
    @Middlewares(middlewareOne)
    @Middlewares(middlewareTwo)

Will log:

two
one

[github-actions]

Hello there winrid 👋

Thank you for opening your very first issue in this project.

We will try to get back to you as soon as we can.👀

[alexbaileyuk]

@winrid have you tried passing them as:

function middlewareOne(req: express.Request, res: express.Response, next: () => void): void {
    console.log('one');
    next();
}

function middlewareTwo(req: express.Request, res: express.Response, next: () => void): void {
    console.log('two');
    next();
}

@Route("comments")
export class CommentsController extends Controller {
    @Get("{tenantId}")
    @Middlewares(middlewareOne, middlewareTwo)

[winrid]

@alexbaileyuk I haven't. I think if that's required it should be called out in the docs.

[alexbaileyuk]

@winrid I don't disagree. I had the same problem a few days ago. I feel like this is due to the way the wrappers work in Typescript more than a TSOA problem though.

[winrid]

@alexbaileyuk I knew I should have migrated this thing to Java instead ^_^ anyway thanks, using a single annotation makes it work fine.

I'll leave this open for now.