variable / @typed/fx/RefHashMap

filterValues

Filter entries creating a Computed value.

Package version
2.0.0-beta.13
Category
Derived queries
Since
1.18.0

Import

import { filterValues } from "@typed/fx/RefHashMap";

Signatures

export declare const filterValues: {
    <K, V>(predicate: (value: V, key: K) => boolean): <E, R>(ref: RefHashMap<K, V, E, R>) => RefSubject.Computed<HashMap.HashMap<K, V>, E, R>;
    <K, V, E, R>(ref: RefHashMap<K, V, E, R>, predicate: (value: V, key: K) => boolean): RefSubject.Computed<HashMap.HashMap<K, V>, E, R>;
};

Why

Projects hash map state with filter values for both current reads and future pushes, avoiding a second mutable cache of the derived value.

Ownership and lifetime

The filter values view retains no independent state. An Effect read samples the source once; Fx observation follows later pushes and its observing Scope owns subscription cleanup.

Other public imports

These import paths expose the same declaration. Each page retains its own public name and signature.

Source