umbraco-context-api

The Umbraco Context API facilitates inter-component communication within the backoffice through context token definitions and provider-consumer patterns. It enables extensions to share data and functionality while remaining decoupled and maintainable.

To consume the UMB_NOTIFICATION_CONTEXT in a TypeScript extension, you access the context to subscribe or retrieve data. This allows your custom extension to display notifications when specific actions occur within the Umbraco backoffice.

Use subscription for ongoing context access when you need your component to react to future data changes, and choose one-time access when you only need the context's current value once without tracking subsequent updates in the Umbraco backoffice.

Yes, you can provide custom contexts to descendant components using the Umbraco Context API provision pattern. This approach allows you to share custom data and functionality down the component tree without direct prop drilling.

TypeScript is the primary language used for demonstrating and implementing the Umbraco Context API. It provides the type safety needed to correctly define context tokens and enforce provider-consumer contracts in backoffice extensions.

Extensions become tightly coupled when components directly reference each other. The Umbraco Context API solves this by using context tokens for communication, allowing you to build decoupled, maintainable extensions that share data indirectly.