serinus-modules-controllers-routes

To organize a Serinus project using a modular architecture, model each feature as a dedicated module with explicit controllers, providers, and imports. This structure enforces scalable module composition and clean separation of concerns across your application.

Register REST routes in Serinus controllers by using the on(...) and onStatic(...) methods. Route prefixes are automatically derived from the controller's defined path, ensuring proper endpoint registration and maintaining route uniqueness per controller.

RequestContext in Serinus controllers is used to properly handle typed request data such as params, query strings, and body. Using typed RequestContext ensures correct data parsing and validation when processing incoming HTTP requests.

The best way to refactor feature modules in a Serinus application is to align with official documentation references and enforce unique per-controller route definitions. This maintains consistency when modifying module composition, controllers, and REST routes.

Defining multiple identical routes in a single Serinus controller is not supported due to enforced route uniqueness. This constraint prevents endpoint conflicts and ensures reliable request mapping when registering routes using on(...).