Support for multi-level/nested folder structure instead of single-level grouping?

[Omid-Zahed]

Hi there!

I have a question about the folder structure for organizing routes. I noticed that Nimbus currently detects and groups routes into multiple folders (e.g., auth, admin, api), which is really helpful. However, it seems like it only supports one level of grouping.

For example, with routes like these:

• auth/login
• auth/register
• admin/users/list
• admin/users/create
• admin/products/list
• admin/products/create

Current behavior:

• Nimbus creates a folder called auth and puts both login and register inside it ✅
• Nimbus creates a folder called admin and puts all four routes inside it (without distinguishing between users and products) ❌

My question is: Is there any plan to support multi-level or tree-like nested folders? So that routes would be organized like this:
📁 auth
└── login
└── register
📁 admin
└── 📁 users
│ └── list
│ └── create
└── 📁 products
└── list
└── create

This would make navigation much cleaner for projects with many endpoints under the same prefix (like admin panels, versioned APIs, etc.).

[sunchayn]

Yes, the first segment is always considered the root resource of the API route. In your case, what you are looking for is what is called multi-application support in Nimbus. So that the admin or any other application is defined separately with its own configuration.

https://github.com/sunchayn/nimbus/tree/base/wiki/user-guide#multi-application-support

Let me know if that answers your use case sufficiently.

[sunchayn]

You can find a live example for the multi-application support in the demo website https://nimbus.sunchayn.io/demo/