umbraco-context-api

To share state across Umbraco backoffice components without tight coupling, use a provider-consumer mechanism with context tokens. This passes data safely through the DOM hierarchy using type-safe UmbContextToken instances.

The difference between consumeContext and getContext in Umbraco involves subscription patterns. Use consumeContext for reactive subscription to context changes, or getContext for one-time static value retrieval from built-in or custom contexts.

To expose custom state to descendant components in Umbraco, use provideContext with a type-safe UmbContextToken. This allows your extension to cascade structured state down the DOM tree to consumers.

Yes, you can access built-in contexts like notifications, current user, and workspace in Umbraco extensions. Consume these contexts using the provider-consumer pattern with appropriate UmbContextToken instances.

Use subscription consumption for Umbraco context API when you need reactive updates to changing state, and one-time consumption with getContext when you only need a static snapshot of the current context value.