Global prefix for a module / route tree

[lukgri]

Hi,

there is an older issue, which got implemented: #40 - allowing to
setGlobalPrefix('api')
on the app instance.

This is a very neat feature and since I'm looking to create some sort of a "route tree", it would be great to set some "route extending strategy".

Say I want to create a route tree like this:
-> api (from app.setGlobalPrefix)
--> /users (UsersModule with prefix 'users' for all of it's 'children' modules and controllers)
---> /posts (PostsModule with prefix 'posts' for all of it's 'children' modules and controllers)
----> /comments (Now I could declare a CommentsController with route 'comments' and this controller's route would be composed from all of the ancestors above, in this case: 'api/users/posts/comments'
----> /upvotes (this one would then be 'api/users/posts/upvotes')

that means I'd like to somehow set the 'module route prefix' for all of it's children's modules & controllers.

If there's already a way to achieve this, please point me in the right direction, otherwise it would be pretty nice to have this.

Thanks

[shekohex]

I'm also looking for something like this , It would be awesome to have a Control of Module prefix
or another way to achieve this

[Zeldaze]

I agree, this will help keep our applications modular. At the moment I must specify my controller base as /api/users, /api/posts, /api/news etc. It's only a small inconvenience for small apps, but a redundancy nevertheless.

[wbhob]

I think there should be a path property on parent modules, like id in Angular modules.

[gelito]

A reference/example on pure Javascript + Express of how to do it:
http://katieleonard.ca/blog/2016/nested-routes-with-expressjs/

It's quite important with the issue #257 because in some cases you have nested elements:

\book:bookHash\chapter:chatperHash

And you want to test that bookHash exists (into the BookController) and also chapterHash exists (into the ChapterController)

[kamilmysliwiec]

The issue is that the modules are not always just a tree. Sometimes they look more like a graph, for example, there might be a module, UsersModule, which contains users business logic and the UsersController inside. The module prefix is users. Now few modules may depend on the UsersModule, but the UsersModule should not 'extend' they API prefixes. Irrelevant whether this is a good practice or not, but it's possible.

[gelito]

@kamilmysliwiec I don't know if it's a good or bad practice, but Angular has the ability of nested routes.

It's not obligatory and is easy to have a workaround, of course, but could be a good improvement.

[kamilmysliwiec]

@gelito nested routes are a good idea, but I can't see a good way to achieve this now. As I said above, module prefix may cause a lot of issues 🙁

[gelito]

Understood!

BTW great job for all!

[lukgri]

isn't there any hack or some sort of middleware that would let us do that?

[wbhob]

What is the possible issue with a module prefix?

[kamilmysliwiec]

@wbhob i have explained it below ^

[ValentinFunk]

Would it be possible to separate routing/controllers and things like services? The same way it's done in Angular for example, where you declare where to mount which modules into the routing tree but you can import and use a module in another without using any of it's routes?

[kamilmysliwiec]

@kamshak hmm.. any ideas about the API? I'm trying to imagine how we could do it well