Middleware for all routes not working with pathless controller and methods

Bug Report

Current behavior

A Middleware configured with forRoutes('*') is not called with a controller without path, such like @Controller(), and also a method without any path, like @Get(). It works with a path in either of them however. The reason behind a pathless controller is I already have a app.setGlobalPrefix('api/...') in my app and I am putting up a controller for that path of global prefix, so no need for a path.

Input Code

//Basically like
NestFactory.create(UserAPIModule, adapter)
  .then(app => {
    app.setGlobalPrefix('api/user');
    app.enableCors();
    return app.init();
  })

// Then...

@Module({
  imports: [UserModule],
})
export class UserAPIModule {
  public configure(consumer: MiddlewareConsumer) {
    consumer.apply(MyMiddleware).forRoutes('*');
  }
}

@Injectable()
export class MyMiddleware implements NestMiddleware {
  public use(req: Request, res: Response, next: Function) {
    console.log('THIS IS NOT CALLED');
    next();
  }
}

@Module({
  imports: []
  controllers: [UserController],
})
export class UserModule {}


@Controller()
export class UserController {
  constructor() {}

  @Get()
  public async getUser() {
    console.log('this is called without middlware');
    return 'Users object';
  }
}

Expected behavior

Middlewares should also be called on pathless controllers due to the meaning of the wildcard

Possible Solution

Environment

Nest version: 6.2.4

 
For Tooling issues:
- Node version: XX  
- Platform:  

Others:

[soumyart]

I’m also facing the same issue. In my use case if you put a trailing slash (http://localhost:3000/api/user/) while accessing the api then middleware is invoked but if you remove the trailing slash (http://localhost:3000/api/user) it is bypassed.

[kamilmysliwiec]

This has been clarified in the documentation (as part of the v7 release) https://docs.nestjs.com/middleware#route-wildcards