umbraco-state-management

To share reactive state across Umbraco backoffice components without tight coupling, implement Umbraco States with observable streams and expose readonly observables from private context properties for elements to consume.

Create an observable state container in an Umbraco context by initializing an UmbStringState or other state type, then wiring observe flows using the Umb*State.asObservable pattern to emit updates to consuming elements.

Derived observable parts in Umbraco state management compute and observe only the relevant slices of an array or object state, reducing unnecessary UI updates by limiting reactivity to specific data changes.

Yes, this approach to Umbraco state management works with Lit elements by wiring context-to-element communication, allowing elements to consume context observables and automatically re-render when the observable emits.

Available Umbraco state types for managing backoffice data include string, number, boolean, array, object, and class states, allowing you to select the correct state type based on your reactive data structure.

You need to fetch the latest Umbraco documentation before implementing state management to ensure you select the correct state type and apply the current Umb*State.asObservable patterns for wiring observe flows accurately.