umbraco-context-api

To share data between Umbraco backoffice components, you use the Umbraco Context API to define context tokens, provide data via provideContext, and consume it in descendants using consumeContext or getContext, ensuring decoupled communication.

The difference between consumeContext and getContext in Umbraco is that consumeContext establishes a subscription for reactive updates, while getContext retrieves the context instance for one-time access without ongoing subscription tracking.

To provide a custom context in Umbraco, you define a context token and call provideContext within a parent component, making your custom data and services available to all descendant components in the backoffice extension.

Yes, you can use TypeScript to implement the Umbraco Context API for a notification system by providing a custom notification context and consuming it across various backoffice views to handle inter-component communication.

You should use the Context API instead of direct component references in Umbraco when building decoupled and maintainable extensions, as it prevents tight coupling and allows seamless data sharing without explicit parent-to-child prop passing.