angular-signals

Angular signals replace BehaviorSubject patterns using writable signal() state and computed() for derived selectors. Leverage RxJS interop functions like toSignal and toObservable to bridge existing Observable data streams into fine-grained reactive state without losing async behavior.

Use linkedSignal in Angular to maintain dependent selections that automatically reset or preserve their chosen state when the underlying source collection updates. This fine-grained reactive approach eliminates manual subscription management and prevents stale selection data.

The resource() API handles parameterized async loading, debounced searches, and optimistic updates in Angular v20+. It exposes loading and error signals directly, allowing components to deterministically track async state without manual Observable subscription wiring.

Angular signals offer synchronous, fine-grained reactive state management that reduces subscription boilerplate compared to RxJS Observables. Use signals for primary state and derived selectors, while reserving RxJS interop for existing async data streams and complex event pipelines.

Test signal-based Angular stores by centralizing state with readonly selectors and exposing loading or error signals. This deterministic reactive behavior allows you to verify state updates and side effects without dealing with asynchronous subscription timing issues.

effect() requires an injection context to run and clean up reactive side effects in Angular v20+. This lifecycle awareness ensures proper cleanup, meaning you should use it within components or services where the injection context is available.