₦airaland Forum

Controller-based routing in Alapa is designed to be intuitive. By following camel-case naming conventions for methods within a controller class, the framework automatically interprets the method names to generate corresponding routes. The first part of the method name specifies the HTTP verb, while the remaining parts define the route path, segmented by uppercase letters.

https://alapa.dev/docs/routing/controller

Controller based routing is a terrible idea.

Imagine an app that has 200 routes, now you will have to go to each controller file to know which route actually exists.

Please put your routes in a separate file.

Karleb:
Controller based routing is a terrible idea.

Imagine an app that has 200 routes, now you will have to go to each controller file to know which route actually exists.

Please put your routes in a separate file.

Thank you very much for your feedback, Karleb. I understand your concern about the complexity of managing routes in large applications.

However, there are various tools and techniques in the Alapa framework that can help you view and manage your routes without having to manually navigate through each controller file. For instance, Alapa provides commands to list all defined routes in one place, which can save time and improve visibility.

You can always group related routes. This way, your routing logic remains organized, and you can avoid the issue of searching through multiple controller files.

In addition, Alapa offers different types of routing strategies apart from controller-based routing, such as Basic routing (similar to Express) and Resource-based routing. You can choose the approach that fits best for your application's structure and needs.

To learn more about these routing options, check out the documentation here: https://alapa.dev/docs/routing/basic

Karleb:
Controller based routing is a terrible idea.

Imagine an app that has 200 routes, now you will have to go to each controller file to know which route actually exists.

Please put your routes in a separate file.

Not always Spring boot and NestJS handles it just fine. Most controllers have a Base endpoint as long as you name it based on your controller, it should be easy to find. But putting in a file seems more organized, but I prefer the decorator approach

Karleb:
Controller based routing is a terrible idea.

Imagine an app that has 200 routes, now you will have to go to each controller file to know which route actually exists.

Please put your routes in a separate file.

or mayBe have the script autoGenerate the routes.

Even Symphony and the likes sef, having to go through controller files just to know name of the route is somewhat a task atimes.

ASP.NET since year 2000 and now .NET Core: Provides greater flexibility, allowing developers to define complex and customized routing schemes as needed.
While:
Alapa: Offers simplicity with automatic route generation, which may be beneficial for standard CRUD operations.