umbraco-controllers

Umbraco backoffice controllers manage timers and subscriptions by extending UmbControllerBase. Implement lifecycle methods like hostConnected() to start timers and hostDisconnected() or destroy() to safely clear them and clean up subscriptions.

To create a reusable controller in Umbraco, extend UmbControllerBase and let it auto-register with the host element. You can access required Umbraco contexts directly within the controller class to compose and reuse UI logic safely.

Calling APIs from an Umbraco backoffice controller requires using the generated OpenAPI client instead of raw fetch. This ensures your controller-driven workflows automatically include the correct Umbraco authentication and configuration.

Handling side effects in Umbraco backoffice UI development is best done by encapsulating them in reusable controllers. This approach separates lifecycle-bound logic like timers and subscriptions from your element code, ensuring safe composition.

Yes, one Umbraco controller can host another to enable controller composition. This pattern allows you to nest reusable logic, where parent controllers manage the lifecycle and context access of their child controllers.

You need hostConnected and hostDisconnected in Umbraco controllers to manage lifecycle-bound side effects. These methods ensure resources like timers and event subscriptions are initialized when the host is active and cleaned up upon disconnection.