serinus-request-pipeline

To organize request processing in Serinus, you centrally orchestrate middleware, hooks, pipes, and exception filters across modules and routes to enforce consistent API behavior. This approach standardizes cross-cutting concerns like validation and authentication globally.

Global, controller, and route scopes in Serinus determine the lifecycle awareness and execution boundaries for hooks and middleware. Applying these scoped components ensures that authentication, validation, and error handling cover only the targeted API endpoints.

To handle uniform error responses in Serinus, you declare and integrate exception filters within your request pipeline. Configuring these filters across global, controller, or route scopes guarantees production-grade error handling for typical API flows.

The best way to enforce input validation and data transformation in a Serinus API is by configuring pipes within your modules. Pipes orchestrate these cross-cutting concerns systematically across your request pipeline for consistent data handling.

Yes, you can apply authentication middleware to specific routes in Serinus without global impact by using route-level or controller-level scopes. This targeted orchestration ensures request processing components only execute where needed.