[Feature, Question] Is it possible to create a controllers' hierarchy? (Similar to using Route in express)

Here is a use-case:

1. I have

@Controller('users')
class UsersController ...

1. Then I have a separate router that handles specific users information, like

@Controller('users/products')
class ProductsController ...

Same applies to URL REST versioning when you need to define couple controllers under the same path prefix:

• /v1/users
• /v1/orders
• /v1/products

This particular case can be resolved with app.setGlobalPrefix('api/v1');

But then we need to support couple API versions, and some of the routes should be reused from the previous version

• /v1/users
• /v2/orders
• /v2/products

How can that be resolved?

[xeoneux]

@kamilmysliwiec this looks like a major use case.

[br0wn]

modules are completely independent of http server

@kamilmysliwiec I’m not sure exactly what you meant by this, could you please elaborate? Since controllers are specified in @Module decorator and they provide routing I was under assumption that modules are in some extent aware of controllers.

My feature request would be to group controllers under common route prefix. Module seems to be prefect place for that as it groups a number of controllers together.

At the moment I’m doing this by having multiple instances of nest app:

async function bootstrap() {
    const server = express();
    const config = require('../../etc/config.js');

    const apiFactory = new NestFactoryStatic();
    const api = await apiFactory.create(ApiModule, server);
    api.setGlobalPrefix("/api/v1");
    await api.init();

    const adminFactory = new NestFactoryStatic();
    const admin = await adminFactory.create(AdminModule, server);
    admin.setGlobalPrefix("/admin");
    await admin.init();

    http.createServer(server).listen(config.server.port);
}

bootstrap();