Nested parameterized routes about nest-router HOT 3 CLOSED

The RouterModule is just adding a prefixes to the all Controllers registered at that Module, so for Example
if we have that route:

{
    path: 'ninja', // the prefix slash is optional
    module: NinjaModule
}

and we registered NinjaController at NinjaModule

...
@Controller(':ninjaId')
export class NinjaController {
    @Get()
    findNinja(@Param('ninjaId') ninjaId) {
        return { ninjaId };
    }
}

so if we hit /ninja/10 it will get { ninjaId: 10 }.
that's have been said.

back to your question, we need to achieve this /ninja/10/cats right ?

in my opinion, each controller - NinjaController & CatsController - thay don't know each others, so instead of defining the param route in the controller scope, you need to define it on the RouterModule schema.
so instead of

{
    path: 'ninja`
    module: NinjaModule,
    children: [{ path: 'cats', module: CatsModule }, ...]
}

you will need to make it like this

{
    path: 'ninja/:ninjaId`
    module: NinjaModule,
    children: [{ path: 'cats', module: CatsModule }, ...]
}

that way, the Controllers registered at CatsModule in our case it is CatsController will be /ninja/:ninjaId/cats, instead of /ninja/cats which was on the first case, also you will need to remove :ninjaId from @Controller(':ninjaId') at NinjaController we don't need it anymore.

and now both NinjaController and CatsController will have access to ninjaId parameter.

give it a shot and let me know if there is any problem 😀

from nest-router.

So, in the previous example, you moved :ninjaId from the controller to the route. What if you need to be able to access ninjas both individually, by id, as well as the whole list of ninjas? Such as:

GET /ninjas -> [{ninjaId: ...}, {ninjaId: ...}]
GET /ninjas/1 -> {ninjaId: 1}

Can this be achieved with this router module, without having to hack the route for /ninjas/:ninjaId to return a list only if ninjaId is falsy?

from nest-router.

Great!
Thank you very much! :)

from nest-router.