hydro-plugin-handler

Hydro plugin route registration maps HTTP endpoints and manages request lifecycles to eliminate repetitive boilerplate. It supports parameter decorators for input handling and response building for structured outputs.

Hydro supports WebSocket integration using lifecycle hooks and inheritance-based patterns for reusable logic. This enables building real-time plugin features while maintaining consistent connection management and extensible route lifecycles.

The best way to manage request lifecycles in Hydro APIs is using parameter decorators, response building, and operation-based action handling to streamline routing. This ensures consistent lifecycle management across HTTP routes and WebSocket handlers.

Yes, you can use parameter decorators for inputs and operation signals for action handling when building Hydro route handlers. These features work together to manage the request lifecycle, build responses, and apply operation-based actions.

To set up a basic HTTP route and WebSocket listener, create a new Hydro plugin project and apply the handler patterns to register endpoints and connection hooks. This provides the foundation for building APIs and real-time features.

Hydro plugin development often requires boilerplate for HTTP routing because manually wiring routes, managing request lifecycles, and integrating WebSocket handlers leads to repetitive code and potential inconsistencies across plugins.